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.
Changes
Implements the
service.ownerentity as proposed in #3101, adding semantic conventions for service ownership information.This enables users to annotate services with organizational ownership details, supporting automation for notifications, incident response, and diagnostics.
New Attributes
service.owner.nameservice.owner.urlservice.owner.contactNew Entity
service.owner- Identifies the team or individual responsible for a serviceservice.owner.nameas identifying attribute (required)service.owner.urlandservice.owner.contactas descriptive attributesStability
All new attributes and the entity are introduced at
developmentstability.Relationship to Existing Conventions
While
service.namespacegroups services logically,service.ownerexplicitly conveys organizational ownership and contact details - addressing a common pattern observed in production environments.Closes #3101
Merge requirement checklist