prometheus / prometheus/OpenMetrics
OM 2.0: Federation: allow distinguishing classic histograms and NHCB
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.5k
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
Problem Statement
From @MichaHoffmann
Assume two (or more) sources for federation. One sends Prometheus classic histograms and the other sends native histograms with custom bucket (NHCB).
Currently OpenMetrics does not allow to expose NHCBs , thus the federated endpoint will show all as classic histograms. This is a loss of information.
Proposed solution
<--! describe the high-level outline of your proposed solution. If the overall direction is accepted and needs more detail, a complete proposal can be written to https://github.com/prometheus/proposals-->
Alternatives considered
<--! describe the high-level outline of alternative solutions you considered, and why you chose your proposed solution over these alternatives-->
- Current state, do not support.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or implementation entry points are identified. Start by reading the issue and the linked Prometheus native histogram custom-bucket specification, then determine how OpenMetrics federation should preserve the distinction between classic histograms and NHCBs. Done means an agreed specification change that prevents this information loss.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100