semantic-conventions
semantic-conventions copied to clipboard
open-telemetry
Defines standards for generating consistent, accessible telemetry across a variety of domains
Fixes #1687 ## Changes The PR is based on the input from the [Mainframe SIG](https://github.com/open-telemetry/sig-mainframe) meetings and is intended to have the discussion to complete the definition of a generic...
### What's missing? The [**Instrument Naming**](https://github.com/open-telemetry/semantic-conventions/blob/4676c009fa6b8f4ed7d2321c991024373e77428e/docs/general/naming.md#instrument-naming) section defines the `*.usage`, `*.limit`, `*.utilization`, and `*.time` metrics, but it does **not** specify their **requirement levels** (Recommended vs. Optional). Because these metrics convey...
### Propose new conventions Knowing what "cpu utilization" means isn’t trivial. There can be different interpretations of it and some users would want control over whether iowait or steal states...
**What are you trying to achieve?** Standardise the configuration for the sanitisation of `db.statement`. With https://github.com/open-telemetry/opentelemetry-specification/issues/3104 the default for the collection of `db.statement` is conditional on whether sanitisation is configured/available...
### Area(s) area:db ### Is your change request related to a problem? Please describe. When sending a command to a database, the parameters may have a type associated with them...
### Area(s) area:gen-ai ### Is your change request related to a problem? Please describe. We have just defined the LLM Semantic Convention, but usually for some RAG apps, the customer...
`*.system` is a compile-time constant which is repetitive on spans and is a good candidate for instrumentation scope attribute. AFAIK, not every OTel api impl supports them (https://github.com/dotnet/runtime/issues/93795, https://github.com/open-telemetry/opentelemetry-java/issues/5503)
This is a belated tracking issue for entity support in semantic conventions split from https://github.com/open-telemetry/opentelemetry-specification/issues/4436. Here is the [proposal](https://docs.google.com/document/d/1GmB0kDx9opHxjj2oy6A4h0fqE8UVW-3ebWgp6zhtbVE/edit?tab=t.0) discussed with semconv + entities groups we're executing against. ## Remaining...
Sometimes there's a good reason not to follow existing guidance, but it can be hard to review semantic conventions without knowing this reasoning, or understanding the scope that the reasoning...
### Area(s) area:gen-ai ### What's missing? There isn't yet a convention for reporting a summary of the arguments. A summary of the arguments is useful where the details might be...
Metadata
Owner
Metadata
Defines standards for generating consistent, accessible telemetry across a variety of domains