opentelemetry-specification
opentelemetry-specification copied to clipboard
open-telemetry
Specifications for OpenTelemetry
**What are you trying to achieve?** Instantaneous exporting of Spans/Traces as they occur, such as when a new Event is added to a Span. What did you expect to see?...
**What are you trying to achieve?** Scope attributes were introduced in #2579 with the motivations behind it described in this [OTEP](https://github.com/open-telemetry/oteps/blob/main/text/0201-scope-attributes.md). A first motivation was to have an attribute to...
**What are you trying to achieve?** Currently `faas.id` is a resource attribute. In AWS Lambda functions its value (lambda function ARN) is only available as a property of the AWS...
After https://github.com/open-telemetry/opentelemetry-specification/pull/368 gets merged we will have support for array values. If we add support for maps and nesting it will allow to represent arbitrary nested data structures in attribute...
Http semantic convention defines 4 attributes which are very different from all others. Namely `http.request_content_length`, `http.request_content_length_uncompressed`, `http.response_content_length` and `http.response_content_length_uncompressed`. I think this information should be captured as metrics, not as...
**What are you trying to achieve?** Make it safe to remove labels from OTLP metrics in a way that preserves their semantics. We have identified two scenarios where it is...
**What are you trying to achieve?** For client-side telemetry (mobile apps, browser apps), it's prohibitive to send spans, metrics and logs separately on different connections. I want to explore ways...
**What are you trying to achieve?** I want to capture request and response bodies. The content can be used for business transaction monitoring and security. To move this forward we...
Should there be a global accessor for LogEmitterProvider? In java (discussed [here](https://github.com/open-telemetry/opentelemetry-java/issues/4081)) we think the answer is no because the global accessor is reserved for API components (i.e. MeterProvider, TracerProvider)...
We got the following feedback in the last end user working group (which was attended by SIG maintainers): >Would be nice if spec changes were somehow pushed out to SIGs....