Define conversion of prometheus native histograms to OpenTelemetry exponential histograms#4561
Merged
jsuereth merged 9 commits intoopen-telemetry:mainfrom Jul 24, 2025
Merged
Conversation
1a3a046 to
9eb6672
Compare
3 tasks
krajorama
reviewed
Jun 25, 2025
Member
krajorama
left a comment
There was a problem hiding this comment.
thank you for starting this, I haven't got around to it yet
…ponential histograms
Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
5ac176e to
bd56bea
Compare
Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
Signed-off-by: Arthur Silva Sens <arthursens2005@gmail.com>
Schemas outside of range are dropped
dashpole
commented
Jul 7, 2025
dashpole
commented
Jul 7, 2025
jmacd
approved these changes
Jul 8, 2025
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
pellared
approved these changes
Jul 22, 2025
Co-authored-by: Robert Pająk <pellared@hotmail.com>
jsuereth
approved these changes
Jul 24, 2025
Merged
via the queue into
open-telemetry:main
with commit Jul 24, 2025
ba9c645
10 of 11 checks passed
Merged
github-merge-queue bot
pushed a commit
that referenced
this pull request
Aug 13, 2025
August 2025 release. ### Logs - Improve concurrency safety description of `LogRecordProcessor.OnEmit`. ([#4578](#4578)) - Clarify that `SeverityNumber` values are used when comparing severities. ([#4552](#4552)) ### Entities - Mention entity references in the stability guarantees. ([#4593](#4593)) ### OpenTelemetry Protocol - Clarify protocol defaults on specification. ([#4585](#4585)) ### Compatibility - Flexibilie escaping of characters that are discouraged by Prometheus Conventions in Prometheus exporters. ([#4533](#4533)) - Flexibilize addition of unit/type related suffixes in Prometheus exporters. ([#4533](#4533)) - Define the configuration option "Translation Strategies" for Prometheus exporters. ([#4533](#4533)) - Define conversion of Prometheus native histograms to OpenTelemetry exponential histograms. ([#4561](#4561)) - Clarify what to do when scope attribute conflicts with name, version and schema URL. ([#4599](#4599)) ### SDK Configuration - Enum values provided via environment variables SHOULD be interpreted in a case-insensitive manner. ([#4576](#4576)) Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Part of #4494
Changes
This conversion is the inverse of the exp -> native conversion defined here: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#exponential-histograms.
CHANGELOG.mdfile updated for non-trivial changes@open-telemetry/prometheus-interoperability @ywwg @krajorama