-
Notifications
You must be signed in to change notification settings - Fork 40.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
Align tag and metric names with Micrometer’s recommendations #30536
Comments
The following are non-compliant tag names: Line 75 in ef79a18
Line 44 in ef79a18
Line 62 in ef79a18
Line 83 in ef79a18
Line 118 in ef79a18
Line 48 in ef79a18
Line 109 in ef79a18
Line 126 in ef79a18
I haven't found any non-compliant metric names. The three GraphQL-related tags are all new in 2.7 so those can be changed without much further thought. The others were added in 2.6 or earlier so renaming them may have an impact on production dashboards. There are a few different options available to us:
I'm going to ask the Observability team for some advice on how best to handle this. |
Camelcase seems fine. I think the problem with hyphens is they can be interpreted as subtraction in some contexts (like a promql query). |
From @shakuzen:
From @jonatan-ivanov:
|
We're going to change all the incompatible tag names to the recommended |
Micrometer recommends that metric and tag names are lower-case and dot-separated. We should review our default metrics and tags to identify those that do not comply with the recommendations. Once we know how many non-compliant names we’re dealing with, we can consider how and when to change them.
Tentatively scheduling for 2.7 but this may get pushed back.
The text was updated successfully, but these errors were encountered: