Skip to content

prometheus: Clarify what to do when scope attribute conflicts with name, version and schema URL #4599

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jsuereth merged 1 commit into from
Jul 24, 2025
Merged

prometheus: Clarify what to do when scope attribute conflicts with name, version and schema URL #4599

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions specification/compatibility/prometheus_and_openmetrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,6 +283,9 @@ the scope schema URL as the `otel_scope_schema_url` label,
the scope attributes as labels with `otel_scope_` prefix and following the rules
described in the [`Metric Attributes`](#metric-attributes) section below,
on all metric points, based on the scope the original data point was nested in.
Scope attributes with names 'name', 'version', or 'schema_url' MUST be dropped
to avoid conflicts with the already existing `otel_scope_name`, `otel_scope_version`, and
`otel_scope_schema_url` labels.
Comment thread
ArthurSens marked this conversation as resolved.
Comment thread
ArthurSens marked this conversation as resolved.

### Gauges

Expand Down
Loading