api: Add a metadata field to UpstreamEndpointStats. (#5154)
Description: This field is used to carry opaque and implementation dependent information of the upstream endpoints. The information may be used by management server for debugging purposes. Example: Consider a requirement of per 'user' load stastics for debugging. Envoy will embed user info into the metadata field for every upstream endpoint it sends load to. This user information will be used by management server for debugging. Sample message: message ClusterStats { cluster_name = ... message UpstreamLocalityStats { locality = ... message UpstreamEndpointStats { address = "endpoint1" metadata = { "user" : "alice"} ... } message UpstreamEndpointStats { address = "endpoint1" metadata = { "user" : "bob"} ... } message UpstreamEndpointStats { address = "endpoint2" metadata = { "user" : "alice"} ... } message UpstreamEndpointStats { address = "endpoint3" metadata = { "user" : "bob"} ... } } } Risk Level: Low Testing: Compiles successfully. Signed-off-by: Karthik Reddy <rekarthik@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 8d8cb4a7c63b74633b0b459af9104143b13f657fpull/620/head
parent
2a08c3e98a
commit
573cbd8136
1 changed files with 5 additions and 0 deletions
Loading…
Reference in new issue