opentelemetry-specification
opentelemetry-specification copied to clipboard
Specifications for OpenTelemetry
**What are you trying to achieve?** There are several combinations of metric instrument and aggregator that OpenTelemetry has not given a formal specification for. Use of these combinations potentially allows...
**What are you trying to achieve?** Trying to address https://github.com/open-telemetry/opentelemetry-js/issues/2997 and https://github.com/open-telemetry/opentelemetry-specification/issues/1891 There are situations when a metrics SDK wants to stop reporting data for a particular instrument and attribute...
**What are you trying to achieve?** I would like http.target to be added in client traces by spec (maybe replacing http.url) **Additional context.** (https://github.com/open-telemetry/opentelemetry-js/issues/3147) As already commented in the above...
**What are you trying to achieve?** Some questions have come up, for example: https://github.com/open-telemetry/opentelemetry-js/issues/3105#issuecomment-1197593270 What did you expect to see? Questions that deserve to be answered for OTLP specifically: -...
The semantic conventions for metrics currently use both spaces and underscores in unit annotations consisting of multiple words. Additionally, we have examples where the spaces between words are just omitted....
## Changes The following PR adds a section to the OTLP exporter about setting a user agent. This was implemented in the otel collector and provides users with additional information...
Part of https://github.com/open-telemetry/opentelemetry-specification/issues/1175 Related to https://github.com/open-telemetry/oteps/pull/210 ## Changes 1. Add a MetricProducer interface to the metrics SDK. It is an optional argument when creating a MetricReader meant to support non-SDK...
Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/2682 ## Changes Add the `short_name` scope attribute. Alternatively, it could have been added as `otel.short_name` to distinguish it from non-otel attributes, or `prometheus.namespace` to make it explicitly associated...
Related: https://github.com/open-telemetry/opentelemetry-specification/issues/1906 This is a second attempt at https://github.com/open-telemetry/opentelemetry-specification/pull/2422. Depends on https://github.com/open-telemetry/opentelemetry-specification/pull/2702 ## Changes 1. Prevent Prometheus naming collisions between instrumentation libraries by adding the short_name as a prefix to...
Resolves https://github.com/open-telemetry/opentelemetry-specification/issues/2532 ## Changes Added semantic conventions for representing feature flags as spans. This can be used to determine the impact a feature has on a request. ## Related issues...