Define configurable SDK component names - #5300
Open
cijothomas wants to merge 7 commits into
Open
cijothomas wants to merge 7 commits into
cijothomas wants to merge 7 commits into
Conversation
Pull request dashboard statusWaiting on the author · refreshed 2026-10-01 18:11 UTC Respond to 2 review items (e.g. link a commit, explain why not, ask a follow-up): Status above doesn't look right?
|
This was referenced Sep 4, 2026
cijothomas
force-pushed
the
cijothomas/component-name-self-observability
branch
from
September 12, 2026 17:13
24b9a98 to
78a898c
Compare
cijothomas
marked this pull request as ready for review
September 22, 2026 15:25
jmacd
approved these changes
Sep 22, 2026
carlosalberto
approved these changes
Sep 25, 2026
pellared
reviewed
Oct 1, 2026
Comment on lines
+15
to
+17
| SDK components MAY allow users to configure an optional name. Users SHOULD | ||
| choose a name that uniquely identifies the component within its containing SDK | ||
| instance. |
Member
There was a problem hiding this comment.
Users SHOULD choose a name
We cannot ensure what users are going to do. We can do something like this instead
If such configuration exists, then it MUST be documented that users should choose...
dashpole
reviewed
Oct 1, 2026
| outlines the mechanisms by which OpenTelemetry components can be configured. It | ||
| does not attempt to specify the details of what can be configured. | ||
|
|
||
| ## SDK component names |
Contributor
There was a problem hiding this comment.
Should we mark this section as in development?
Suggested change
| ## SDK component names | |
| ## SDK component names | |
| **Status**: [Development](../document-status.md) |
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
6 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.
Fixes #5298
Changes
Define optional names that uniquely identify SDK components within their containing SDK instance.
Component names may be used by configuration and management mechanisms. When a named component emits self-observability telemetry, it uses the application-provided value as
otel.component.name. If no name is configured, it automatically assigns a name satisfying theotel.component.namesemantic convention.This preserves automatic naming for applications that do not configure a name while allowing future mechanisms to refer to individual component instances.
Related changes
Together, these changes define configurable SDK component names, their fallback naming convention, and declarative configuration support.
Recommend default SDK component name format semantic-conventions#4082
schema: add SDK component names opentelemetry-configuration#737
Related issue Allow applications to assign names to SDK components #5298
Related OTEPs: not applicable
Links to prototypes: schema: add SDK component names opentelemetry-configuration#737
CHANGELOG.mdupdatedSpec compliance matrix: not applicable; no common API shape is required
Declarative configuration support is provided by schema: add SDK component names opentelemetry-configuration#737