Skip to content

fix(om2.0): fixes in type text format #2903

Open
krajorama wants to merge 1 commit intomainfrom
krajo/om2-text-types
Open

fix(om2.0): fixes in type text format #2903
krajorama wants to merge 1 commit intomainfrom
krajo/om2-text-types

Conversation

@krajorama
Copy link
Member

The one major fix is that a gauge histogram doesn't have start time.

The one major fix is that a gauge histogram doesn't have start time.

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
@krajorama krajorama added the priority/p2 Candidates for next primary. label Mar 18, 2026
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the OpenMetrics 2.0 text-format specification to clarify value constraints for scalar metric types, improve cross-references/examples, and correct GaugeHistogram guidance to align with the data model (notably around Start Timestamp usage).

Changes:

  • Adds explicit “Sample value MUST be a Number” statements for Gauge/Counter/Unknown in the text-format metric type sections.
  • Improves spec text clarity (adds UTF-8 Quoting anchor link, refines example descriptions, adds a note about native bucket values being absolute counts).
  • Adjusts GaugeHistogram text-format examples and descriptions, including removing st@... from a GaugeHistogram example.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority/p2 Candidates for next primary.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants