Skip to content

Management Server Identification #5770

@ramaraochavali

Description

@ramaraochavali

Some times we would like to know to which management server instance, the running Envoy is connected to debug certain scenarios. Currently there is no provision to do that.

The proposal is to include a opaque identifier in DiscoveryResponse (similar to opaque identifier in Node of DiscoveryRequest) that management server can populate and send. On the Envoy side we can push a gauge stat indicating the management server identifier.

What do you think about this? Would you think it would be generally useful or leave it to the management server to figure that out by some logging etc.

Metadata

Metadata

Labels

design proposalNeeds design doc/proposal before implementationenhancementFeature requests. Not bugs or questions.stalestalebot believes this issue/PR has not been touched recently

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions