Clarify declarative config default requirements#4780
Merged
jack-berg merged 6 commits intoopen-telemetry:mainfrom Dec 15, 2025
Merged
Clarify declarative config default requirements#4780jack-berg merged 6 commits intoopen-telemetry:mainfrom
jack-berg merged 6 commits intoopen-telemetry:mainfrom
Conversation
carlosalberto
approved these changes
Dec 5, 2025
…y-specification into clarify-declarative-config-default-behavior
maryliag
approved these changes
Dec 9, 2025
tsloughter
approved these changes
Dec 10, 2025
…y-specification into clarify-declarative-config-default-behavior
…rds, create is responsible for semantics defined in description
Merged
Merged
zeitlinger
pushed a commit
to zeitlinger/opentelemetry-specification
that referenced
this pull request
Jan 9, 2026
### Metrics - Stabilize part of `Enabled` SDK for synchronous instruments. ([open-telemetry#4787](open-telemetry#4787)) ### Logs - Add optional Ergonomic API. ([open-telemetry#4741](open-telemetry#4741)) ### SDK Configuration - Declarative configuration: clarify default behavior and validation requirements of `create` and `parse`. ([open-telemetry#4780](open-telemetry#4780)) - Declarative configuration: add optional programmatic customization to `create`, and add related supplemental guidelines. ([open-telemetry#4777](open-telemetry#4777)) - Declarative configuration: add links between SDK extension plugins and corresponding declarative config types. ([open-telemetry#4802](open-telemetry#4802)) - Declarative configuration: clarify Registry ComponentProvider `type` parameter ([open-telemetry#4799](open-telemetry#4799)) ### Common - Stabilize complex `AnyValue` attribute value types and related attribute limits. ([open-telemetry#4794](open-telemetry#4794))
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
5 participants
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.
When the declarative config
createspec was written, declarative config was dependent on the spec as its source of truth for default values for the various properties.We now directly record expected
defaultBehaviorandnullBehaviorsemantics inopentelemetry-configuration.Updating the spec to tie things back together.
/cc @open-telemetry/configuration-approvers