Use consistent vocabulary in reference to components and plugins#4806
Merged
jack-berg merged 9 commits intoopen-telemetry:mainfrom Jan 9, 2026
Merged
Conversation
jack-berg
commented
Dec 15, 2025
…y-specification into consistent-component-vocabulary
carlosalberto
approved these changes
Dec 18, 2025
|
This PR was marked stale. It will be closed in 14 days without additional activity. |
codeboten
reviewed
Jan 5, 2026
…y-specification into consistent-component-vocabulary
robsunday
reviewed
Jan 7, 2026
Member
Author
|
Thanks for the review @robsunday! |
robsunday
approved these changes
Jan 9, 2026
maryliag
approved these changes
Jan 9, 2026
codeboten
approved these changes
Jan 9, 2026
…y-specification into consistent-component-vocabulary
Merged
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 13, 2026
### Context - Deprecate Jaeger propagator and make propagator implementation optional. ([#4827](#4827)) - Deprecate OT Trace propagator and make propagator implementation optional. ([#4851](#4851)) ### Metrics - Add normative language to the Metrics API/SDK spec concurrency requirements. ([#4868](#4868)) ### Logs - Add optional `Exception` parameter to Emit LogRecord. ([#4824](#4824)) - Add normative language to the Logging API/SDK spec concurrency requirements. ([#4885](#4885)) ### Resource - Refine the handling of OTEL_RESOURCE_ATTRIBUTES. ([#4856](#4856)) ### Common - Add string representation guidance for complex attribute value types (byte arrays, empty values, arrays, and maps) for non-OTLP protocols. ([#4848](#4848)) ### Compatibility - Stabilize Prometheus Counter to OTLP Sum transformation. ([#4862](#4862)) - Stabilize Prometheus Gauge to OTLP Gauge transformation. ([#4871](#4871)) ### SDK Configuration - Swap Tracer/Meter/LoggerConfig `disabled` for `enabled` to avoid double negatives ([#4823](#4823)) - Declarative configuration: rename `ComponentProvider` to `PluginComponentProvider`, `CreatePlugin` to `CreateComponent` in effort to use consistent vocabulary ([#4806](#4806)) - Declarative configuration: Update instrumentation config behavior to return empty object when not set ([#4817](#4817))
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.
In response to this feedback: #4568 (comment)
The declarative config SDK spec uses "component", "extension plugin interface", "SDK extension plugins" somewhat interchangeable.
This PR makes the vocabulary consistent:
To facilitate, this PR:
ComponentProvidertoPluginComponentProvider. This makes it clear that only plugins are being provided rather than all components.ComponentProvider.createPlugintoPluginComponentProvider.createComponent.There are no functional changes in this PR, just naming updates.