prometheus/docs
1
0
Fork 0
mirror of https://github.com/prometheus/docs.git synced 2026-02-05 06:45:01 +01:00
Code Issues Releases Activity

feat(om2): exemplar timestamp MAY to SHOULD (#2775)

Browse Source 
Make the exemplar timestamp a SHOULD in preparation for complex types
having multiple exemplars at a time. We'll explain why having timestamp
for exemplars of complex types is a good idea there.

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
This commit is contained in:
George Krajcsovits
2025-11-20 08:40:58 +01:00
committed by GitHub
parent 9e02fa111c
commit 60c24e4500
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/specs/om/open_metrics_spec_2_0.md
View File

@@ -108,7 +108,7 @@ Each MetricPoint consists of a set of values, depending on the MetricFamily type
Exemplars are references to data outside of the MetricSet. A common use case are IDs of program traces.
Exemplars MUST consist of a LabelSet and a value, and MAY have a timestamp. They MAY each be different from the MetricPoints' LabelSet and timestamp.
Exemplars MUST consist of a LabelSet and a value, and SHOULD have a timestamp. They MAY each be different from the MetricPoints' LabelSet and timestamp.
The combined length of the label names and values of an Exemplar's LabelSet MUST NOT exceed 128 UTF-8 character code points. Other characters in the text rendering of an exemplar such as `",=` are not included in this limit for implementation simplicity and for consistency between the text and proto formats.