⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@jpkrohling
Copy link
Member

Changes

Implements the service.owner entity 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

Attribute Type Description
service.owner.name string Name of the team or individual responsible for the service
service.owner.url string URL to the service's source code repository or documentation
service.owner.contact string Contact point or communication channel (e.g., Slack, email)

New Entity

  • service.owner - Identifies the team or individual responsible for a service
    • service.owner.name as identifying attribute (required)
    • service.owner.url and service.owner.contact as descriptive attributes

Stability

All new attributes and the entity are introduced at development stability.

Relationship to Existing Conventions

While service.namespace groups services logically, service.owner explicitly conveys organizational ownership and contact details - addressing a common pattern observed in production environments.

Closes #3101

Merge requirement checklist

Signed-off-by: Juraci Paixão Kröhling <[email protected]>
@jpkrohling jpkrohling force-pushed the jpkroehling/otel-154-add-serviceowner-entity-semantic-conventions branch from a379a64 to bc4e101 Compare January 11, 2026 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:service enhancement New feature or request

Projects

Development

Successfully merging this pull request may close these issues.

Proposal: Add service.owner entity

1 participant