opentelemetry-specification
opentelemetry-specification copied to clipboard
open-telemetry
Specifications for OpenTelemetry
**What are you trying to achieve?** I started working on implementing the HTTP retry spec in the Java HTTP client instrumentations, and I ran into several questions that I'd like...
_This is a high-level tracking issue to track items across several github repos._ Languages: - [ ] Java - [ ] JS - [ ] Python - [ ] Go...
Fixes #3867. This introduces the concept of scope-level configuration for Tracer, Meter, and Logger. Notes: - TracerProvider, MeterProvider, and LoggerProvider have a scope config provider function, which accepts an `InstrumentationScope`...
## What https://github.com/open-telemetry/opentelemetry-specification/blob/e8d5e1416a6a491f0fc26df60a5a2bd41535a8ca/specification/logs/data-model.md#type-mapstring-any should allow having duplicate keys. ## Why ### Performance Checking for duplicates introduces performance overhead which can be undesirable for systems where logging should be high-performant. Changing...
Resolve #3565 ## Changes The output format of the STDOUT exporter is unique to each OpenTelemetry language implementation. Reflect this in the specification and add normative requirements and suggestions for...
The conversation about whether [file configuration](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/file-configuration.md) should completely ignore the [sdk environment variable scheme](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md) [came up](https://github.com/open-telemetry/opentelemetry-specification/pull/3744#issuecomment-1785665250) in #3744, but that PR doesn't actually contain any language related to this. The...
- Followup to #3939 - Drops the leading "OpenTelemetry" in exporter page titles, where relevant. - For example, I kept "OpenTelemetry" in titles like "OpenTelemetry to Jaeger Transformation"
**What are you trying to achieve?** From: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/file-configuration.md#environment-variable-substitution > For example, `${API_KEY}` is valid, while `${1API_KEY}` and `${API_$KEY}` are invalid. I think saying "invalid" does not make it clear how...
**What are you trying to achieve?** Reference: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/file-configuration.md#environment-variable-substitution I would like to set a string value to `${NOT_ENV_VAR}` and make sure it is not escaped. **Additional context.** I think that...
**What are you trying to achieve?** Mark the [Overflow attribute](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#overflow-attribute) section under Cardinality limits as **Stable**. The spec was updated with the overflow attribute and cardinality limits section in #2960....
