opentelemetry-specification icon indicating copy to clipboard operation
opentelemetry-specification copied to clipboard

Specifications for OpenTelemetry

Results 344 opentelemetry-specification issues
Sort by recently updated
recently updated
newest added

**What are you trying to achieve?** I would like to add missing environment variables to configure compression on (span) exporters to the [OpenTelemetry Environment Variable Specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md) and clarify the compression...

spec:miscellaneous
area:configuration
triaged-needmoreinfo

Fixes #2860 Mostly adds specifics for log attribute limit configuration, but also refactors the wording of the span specifics as I found it a bit confusing.

The term "distribution" should be defined in the spec (e.g. glossary) given that it is already described under https://opentelemetry.io/docs/concepts/distributions/.

spec:miscellaneous

**What are you trying to achieve?** For our documentation at opentelemetry.io I tried to come up with a quick statement on "where is the OpenTelemetry agent"? (https://github.com/open-telemetry/opentelemetry.io/issues/1689 for reference, don't...

spec:miscellaneous

I'm not 100% sure this addition is needed to make it clear but after seeing the issue that truncation can create invalid utf8 in some languages I wanted to ensure...

Stale

Fixes #2839 ## Changes Add structured stacktrace to exception attributes. The stacktrace is broken up to 4 attributes: `exception.structured_stacktrace.function_names`, `exception.structured_stacktrace.filenames`, `exception.structured_stacktrace.line_numbers`, `exception.structured_stacktrace.column_numbers` This may be premature to open but I...

Stale

**What are you trying to achieve?** Find out what is the right JSON format. What did you expect to see? The right format to follow **Additional context.** OTel log format...

spec:logs
triaged-accepted

We should outline what changes to metric streams (names, unit, type + attributes) constitutes a breaking change. More details to follow

area:semantic-conventions
spec:metrics

I'd like to propose that we drop support for the `jaeger-thrift` exporter. The [upstream repo](https://github.com/jaegertracing/jaeger-client-java) has been marked deprecated and they're actively encouraging folks to use OpenTelemetry instead. They're also...

The specification _kind of_ implies that attributes limits also apply to logs, but much of the spec is very span-centric. Add details of log-specific attribute limit configuration matching the trace...

spec:logs