semantic-conventions icon indicating copy to clipboard operation
semantic-conventions copied to clipboard

Defines standards for generating consistent, accessible telemetry across a variety of domains

Results 442 semantic-conventions issues
Sort by recently updated
recently updated
newest added

Fixes #2245 ## Changes Adds rationale and further guidance for naming Kubernetes resources. ## Merge requirement checklist * [ x] [CONTRIBUTING.md](https://github.com/open-telemetry/semantic-conventions/blob/main/CONTRIBUTING.md) guidelines followed. * [ x] Change log entry added,...

enhancement
area:k8s

### Area(s) area:gen-ai ### What's missing? Although there are existing events for tool calling (`gen_ai.assistant.message`, `gen_ai.tool.message`), these are more geared towards the Gen AI model's view of what tools should...

area:code
area:gen-ai

Fixes #2053 ## Changes Defines a `gcp.gen_ai.operation.config.` dynamic attribute in support of Google Gen AI SDK instrumentation (see: [PR 3374: include more request configuration options...](https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3374)). In support of this change,...

enhancement
area:gcp
area:gen-ai

### Area(s) area:feature-flag ### What's missing? The FF SemConv SIG believes after #1990 we will be ready for release candidate. This is a placeholder issue where the members of the...

triage:needs-triage
area:feature-flag

The k8s migration guide should link to specific SemConv releases (once those are available) for any introduced breaking changes. This PR fixes the already existing ones. I could not come...

### Area(s) area:cloudevents ### What's missing? The ability to specify the data content type as available in the base core spec: https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md ### Describe the solution you'd like The below...

triage:needs-triage
area:cloudevents

### Area(s) area:messaging ### What's missing? The ability to specify the message content type ### Describe the solution you'd like The below attributes are added to the spec so that...

triage:needs-triage
area:messaging

### Area(s) area:http ### What's missing? The ability to specify the body content type ### Describe the solution you'd like The below attributes are added to the spec so that...

triage:needs-triage
area:http

The [messaging span spec](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/messaging/messaging-spans.md#recording-per-message-attributes-on-batch-operations) tells that for batch receive/process scenarios span attributes which differ per message should be set on the links describing the message. How to do that in...

area:messaging

Follow-up to #2175 cc @odubajDT

Skip Changelog