Skip to content

fix(om2): consistency between model and exposition#2890

Open
krajorama wants to merge 2 commits intomainfrom
krajo/om2-should-meta
Open

fix(om2): consistency between model and exposition#2890
krajorama wants to merge 2 commits intomainfrom
krajo/om2-should-meta

Conversation

@krajorama
Copy link
Member

The model said that: A MetricFamily MUST have a name, HELP, TYPE, and UNIT
metadata. However the exposition does not require it to be exposed,
therefore for the sake of consistency we make this SHOULD. Also having all caps conflated the model with the exposition.

Also this allows very simple exposers to not think about this.

krajorama and others added 2 commits March 12, 2026 09:27
The model said that: A MetricFamily MUST have a name, HELP, TYPE, and UNIT
 metadata. However the exposition does not require it to be exposed,
therefore for the sake of consistency we make this SHOULD.
Also having all caps conflated the model with the exposition.

Also this allows very simple exposers to not think about this.

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
#### MetricFamily

A MetricFamily MAY have zero or more Metrics. A MetricFamily MUST have a name, HELP, TYPE, and UNIT metadata. Every Metric within a MetricFamily MUST have a unique LabelSet.
A MetricFamily MAY have zero or more Metrics. Every Metric within a MetricFamily MUST have a unique LabelSet. A MetricFamily SHOULD have a name, Help, Type, and Unit metadata.
Copy link
Contributor

Choose a reason for hiding this comment

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

well... You do definitely need a name, so we should probably keep that as a must

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants