Skip to content

[Prometheus and OpenMetrics] Handle scheme URL and scope attributes as identifying #4223

Closed
@pellared

Description

@pellared

I think this needs updates to some of the compatibility docs (at least prometheus). Currently, Prometheus adds scope name and scope version as labels to ensure we don't end up with duplicate timeseries, and we are able to put scope attributes in a separate otel_scope_info metric. With this change, we will need to update this to instead add the scope name, scope version, and scope attributes to all metrics.

TIL schema_url is also identifying, so that is something we will need to handle in Prometheus export and other "non-OTLP" compatibility documents.

Originally posted by @dashpole in #4161 (comment)

Metadata

Metadata

Labels

sig-issueA specific SIG should look into this before discussing at the specspec:metricsRelated to the specification/metrics directorytriage:accepted:readyReady to be implemented. Small enough or uncontroversial enough to be implemented without sponsor

Type

No type

Projects

Status

Spec - Closed

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions