semantic-conventions
semantic-conventions copied to clipboard
Defines standards for generating consistent, accessible telemetry across a variety of domains
Fixes #792 ## Changes This PR introduces the a metric for messaging systems to report the time difference from which a message was produced to when it was consumed. This...
### Area(s) area:k8s ### Is your change request related to a problem? Please describe. At the moment there are not Semantic Conventions for k8s metrics. ### Describe the solution you'd...
Fixes https://github.com/open-telemetry/semantic-conventions/issues/996 ## Changes Please provide a brief description of the changes here. Note: if the PR is touching an area that is not listed in the [existing areas](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/README.md), or...
### Area(s) area:gen-ai, llm ### Is your change request related to a problem? Please describe. Continuation of https://github.com/open-telemetry/semantic-conventions/issues/1007 To prevent threats to LLM systems, such as misuse, and to log...
### Area(s) area:new ### Is your change request related to a problem? Please describe. As discussed in the following PR that contributes Azure logs transformations to the OpenTelemetry Collector Contrib,...
This PR changes the semantics behind `host.id` calculation for Cloud. ## Changes In Cloud, it is possible for `instance_id` to not be retrievable from inside the instance (e.g. security concerns...
We probably need to standardize operation name (as attribute) - e.g. openai object like "chat.completion" or "embedding" and use the operation name inside the span name as well.
Related to #860 Alternative proposal to #961 ## Changes Specific URL query string values should now be redacted by default due to concerns around leaking credentials. The list of problematic...
In the #825 we only mention `openai`, but we should pick a set of vendors/systems we want to support and prototype/validate if attributes/events are applicable to them.