-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add DC and NS support for Envoy metrics #9207
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/283055. |
🍒✅ Cherry pick of commit fe72885 onto |
This PR updates the tags that we generate for Envoy stats. Several of these come with breaking changes, since we can't keep two stats prefixes for a filter.
This PR updates the tags that we generate for Envoy stats. Several of these come with breaking changes, since we can't keep two stats prefixes for a filter.
Updated version of: #9117
This PR updates the tags that we generate for Envoy stats.
Several of these come with breaking changes, since we can't keep two stats prefixes for a filter.
For destination clusters:
consul.destination.[namespace|service|subset|hash|datacenter|etc...]
consul.[service|etc..]
to disambiguate between cluster and listener filter labels.For upstream listeners:
consul.upstream.[namespace|service|datacenter|protocol]
For the local cluster:
consul.source.[namespace|service|datacenter]
Note: The delimiter for gateway-related Envoy metrics was updated from
_
to.
.