OTEP: Federated SemConv and Schema v2 - #4815
Merged
Merged
Conversation
jsuereth
reviewed
Jan 3, 2026
jsuereth
left a comment
Contributor
There was a problem hiding this comment.
Great draft!
Added my initial thoughts. Let me know if you need help writing any section.
benkawecki
reviewed
Jan 5, 2026
lmolkova
commented
Jan 6, 2026
lmolkova
commented
Jan 6, 2026
lmolkova
commented
Jan 6, 2026
atoulme
reviewed
Jan 7, 2026
jsuereth
reviewed
Jan 27, 2026
jsuereth
reviewed
Jan 27, 2026
jsuereth
reviewed
Jan 30, 2026
|
|
Member
Author
|
will fix easy cla prior to merge (want to preserve commit hashes mentioned in discussions) |
florianl
approved these changes
May 12, 2026
MikeGoldsmith
approved these changes
May 13, 2026
12 tasks
Contributor
|
It has been weeks without further comments or feedback, and we have the four required approvals we need for OTEPs. We can iron out details when incorporating these changes into the Specification. Merging. |
atoulme
approved these changes
May 15, 2026
atoulme
left a comment
Contributor
There was a problem hiding this comment.
LGTM - looking forward to adopting in the collector
lmolkova
force-pushed
the
semconv-schema-v2
branch
from
May 17, 2026 17:39
36285a9 to
bab8479
Compare
Merged
pellared
pushed a commit
to pellared/opentelemetry-specification
that referenced
this pull request
May 19, 2026
pull Bot
pushed a commit
to CodeWeaver13/opentelemetry-specification
that referenced
this pull request
May 20, 2026
### Metrics - Add in-development `Bind` API to synchronous instruments. ([open-telemetry#5050](open-telemetry#5050)) - Clarify that View-provided metric stream `name` is not subject to instrument name syntax validation. ([open-telemetry#5094](open-telemetry#5094)) ### Common - Define the Core packages term. ([open-telemetry#5046](open-telemetry#5046)) - Rework contributing guide to reflect current process. ([open-telemetry#5072](open-telemetry#5072)) ### Compatibility - Stabilize sections of Prometheus and OpenMetrics Compatibility. - Stabilize translation of labels prefixed with `otel_scope_` to OTLP Instrumentation Scope. ([open-telemetry#5004](open-telemetry#5004)) - Stabilize OpenTelemetry Gauge and Sum to Prometheus transformations. ([open-telemetry#5034](open-telemetry#5034)) - Stabilize OpenTelemetry Instrumentation Scope to Prometheus labels transformation. ([open-telemetry#5052](open-telemetry#5052)) - Stabilize sections of Prometheus Metrics Exporter. - Stabilize temporality. ([open-telemetry#5024](open-telemetry#5024)) - Stabilize version and format. ([open-telemetry#5083](open-telemetry#5083)) - Stabilize port configuration. ([open-telemetry#5026](open-telemetry#5026)) - Stabilize `scope_info_enabled` configuration. ([open-telemetry#5056](open-telemetry#5056)) - Change Prometheus Metric Exporter config property recommended names (`without_scope_info` -> `scope_info_enabled`, `without_target_info` -> `target_info_enabled`, `with_resource_constant_labels` -> `resource_constant_labels`) ([open-telemetry#5071](open-telemetry#5071)) - Clarify that OTel SDKs should not use unofficial Prometheus clients. ([open-telemetry#5082](open-telemetry#5082)) ### OTEPs - Add OTEP for Semantic Convention Schema v2 with support for multiple convention registries and resolved schema format ([open-telemetry#4815](open-telemetry#4815)) --------- Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
hilmarf
pushed a commit
to apeirora/opentelemetry-specification
that referenced
this pull request
Jun 1, 2026
hilmarf
pushed a commit
to apeirora/opentelemetry-specification
that referenced
this pull request
Jun 1, 2026
### Metrics - Add in-development `Bind` API to synchronous instruments. ([open-telemetry#5050](open-telemetry#5050)) - Clarify that View-provided metric stream `name` is not subject to instrument name syntax validation. ([open-telemetry#5094](open-telemetry#5094)) ### Common - Define the Core packages term. ([open-telemetry#5046](open-telemetry#5046)) - Rework contributing guide to reflect current process. ([open-telemetry#5072](open-telemetry#5072)) ### Compatibility - Stabilize sections of Prometheus and OpenMetrics Compatibility. - Stabilize translation of labels prefixed with `otel_scope_` to OTLP Instrumentation Scope. ([open-telemetry#5004](open-telemetry#5004)) - Stabilize OpenTelemetry Gauge and Sum to Prometheus transformations. ([open-telemetry#5034](open-telemetry#5034)) - Stabilize OpenTelemetry Instrumentation Scope to Prometheus labels transformation. ([open-telemetry#5052](open-telemetry#5052)) - Stabilize sections of Prometheus Metrics Exporter. - Stabilize temporality. ([open-telemetry#5024](open-telemetry#5024)) - Stabilize version and format. ([open-telemetry#5083](open-telemetry#5083)) - Stabilize port configuration. ([open-telemetry#5026](open-telemetry#5026)) - Stabilize `scope_info_enabled` configuration. ([open-telemetry#5056](open-telemetry#5056)) - Change Prometheus Metric Exporter config property recommended names (`without_scope_info` -> `scope_info_enabled`, `without_target_info` -> `target_info_enabled`, `with_resource_constant_labels` -> `resource_constant_labels`) ([open-telemetry#5071](open-telemetry#5071)) - Clarify that OTel SDKs should not use unofficial Prometheus clients. ([open-telemetry#5082](open-telemetry#5082)) ### OTEPs - Add OTEP for Semantic Convention Schema v2 with support for multiple convention registries and resolved schema format ([open-telemetry#4815](open-telemetry#4815)) --------- Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposes a new telemetry schema format so OTel Collector, instrumentation libs, and third parties can publish their own conventions with dependencies on OTel semconv.
What's new:
1.39.0(stable only) vs1.39.0-dev(everything)opentelemetry.io/schemas/{component}/{version}for per-repo schemasBreaking:
1.1.0(the diff format)