-
Notifications
You must be signed in to change notification settings - Fork 946
Update Prometheus client to 1.5.0 #8080
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
Merged
jack-berg
merged 1 commit into
open-telemetry:main
from
zeitlinger:update-prom-client-simple
Feb 25, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@zeitlinger when I look into the code I see
prometheusNamecallsescapeName(String, EscapingScheme), whereEscapingSchemeis an enum with values: ALLOW_UTF8, UNDERSCORE_ESCAPING, DOTS_ESCAPING, VALUE_ENCODING_ESCAPINGAnd I've seen some hints in the code that the metric and attribute name escaping is influenced by headers requested by the client. Do we need to escape at all or will prometheus do we want by default?
Also, we've had offline conversations about the prometheus client library automatically appending suffixes like
_totaland units, and not providing an opt out mechanism, which makes it problematic for us in opentelemetry-java to implement the translation strategy option. Want to confirm this is still the case with this new version. Seems a bit strange that prometheus would have facilities to produce a full unescaped utf8 metric name but still always produces metric names with the suffixes.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.
Escaping: You're right that the escaping scheme is normally determined at scrape time based on the
Acceptheader (EscapingScheme.fromAcceptHeader()). By callingprometheusName()here, we're pre-escaping to underscores at snapshot creation time, so even if a scraper requestsescaping=allow-utf-8, it would still get underscore-escaped names.This is intentional for this PR — the goal is just to maintain backward-compatible behavior after the 1.5.0 upgrade (where
sanitizeMetricName/sanitizeLabelNameno longer do underscore escaping themselves). UTF-8 support will be unlocked by implementing the translation strategy option, which controls whether names are escaped to legacy format or kept as-is.Suffixes: Yes, the Prometheus client still hardcodes
_totalin the text format writer forCounterSnapshotwith no opt-out. Unit suffixes are already handled by the OTel exporter itself (inconvertMetadata), so those aren't a problem. The_totalsuffix is the blocker for the translation strategy option (prometheus/client_java#1555). The plan is to add adisableSuffixAppendingflag as part of experimental OpenMetrics 2.0 support (prometheus/client_java#1912), which will also unblock the OTel translation strategies.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.
Makes sense. I'll leave this unresolved so I can find it easier when we come back to the translation strategy work.