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

The [changelog](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CHANGELOG.md) in the spec repo has to be updated manually for each PR but sometimes PR authors forget to do so. Relying on reviewers to catch this is error-prone....

help wanted
editorial

In OpenTracing, we have `CHILD_OF` and `FOLLOWS_FROM`. In the new project, we are considering whether to include this concept as a flag on the `SpanBuilder` option when setting the span...

area:api
area:sampling
area:span-relationships
spec:trace
spec:protocol
release:after-ga

Currently it is possible to refer to a Resource in spans and metrics. The Resource indicates where the signal was generated. However, we may need a way to reference the...

area:api
spec:resource
release:after-ga

This is to follow up the non-blocking comment https://github.com/open-telemetry/opentelemetry-specification/pull/2404#discussion_r828331793. Discussed during the 3/18/2022 triage meeting, we consider this as a nice wording change which doesn't block #2404.

area:sdk
spec:metrics
release:allowed-for-ga

All the 3 data types can be validated at design time using static analysis and also evaluated at run-time. For metrics exposed in Prometheus exposition format, we have Promtool, an...

question
spec:miscellaneous

The prometheus conversion currently requires metric names to be modified with the OTLP unit > Additionally, the unit MUST be added as a suffix to the metric name, and SHOULD...

spec:metrics
triage:deciding:needs-info

Currently, instrumentation_scope is not used in the documentation for converting OTLP metrics to Prometheus. However, because it is part of identity for the OTLP model, it should be added as...

spec:metrics

**What are you trying to achieve?** The client-side instrumentation SIG is working on defining telemetry for client-side applications, and we believe that we need a way to classify this telemetry...

area:semantic-conventions
spec:resource
triage:deciding:needs-info

OpenMetrics spec gives explicit advice to not include timestamps in exported data. https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#exposing-timestamps So we should probably follow this. Currently, we only mention timestamps for exemplars https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/datamodel.md#exemplars-2 We should remove...

spec:metrics

Strictly speaking `scheme` is not an HTTP concept. https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml

area:semantic-conventions