Skip to content

proposal: Prometheus internal telemetry as an OTel semantic convention registry#86

Draft
nicolastakashi wants to merge 3 commits into
prometheus:mainfrom
nicolastakashi:semconv-internal-telemetry
Draft

proposal: Prometheus internal telemetry as an OTel semantic convention registry#86
nicolastakashi wants to merge 3 commits into
prometheus:mainfrom
nicolastakashi:semconv-internal-telemetry

Conversation

@nicolastakashi

@nicolastakashi nicolastakashi commented Jun 27, 2026

Copy link
Copy Markdown

This proposal defines all metrics exported by the Prometheus binary as a formal OTel semantic convention registry. Making the schema machine-readable enables auto-generated instrumentation code, always-in-sync documentation, contract testing against live instances, and a lifecycle model for safe metric evolution across the Prometheus ecosystem.

Proof-of-concept implementation: prometheus/prometheus#17868

…n registry

Signed-off-by: Nicolas Takashi <nicolas.tcs@hotmail.com>
@nicolastakashi
nicolastakashi force-pushed the semconv-internal-telemetry branch from 495ef5e to 5a8157f Compare June 27, 2026 20:10
…naming, and rename to PROM-86

Signed-off-by: Nicolas Takashi <nicolas.tcs@hotmail.com>
@nicolastakashi
nicolastakashi force-pushed the semconv-internal-telemetry branch from 459e052 to 293d5de Compare June 29, 2026 09:46
…iming

Signed-off-by: Nicolas Takashi <nicolas.tcs@hotmail.com>
@roidelapluie

Copy link
Copy Markdown
Member

I would like to assess what alternatives we have that could be built-in e.g. client_golang and would be lighter. And I would also want to better understand the scope of this: a lifecycle model for safe metric evolution across the Prometheus ecosystem.

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