opentelemetry-specification
opentelemetry-specification copied to clipboard
open-telemetry
Specifications for OpenTelemetry
Some APIs accept lists of attributes. The spec does not define the behavior if the attributes are mutated after the API call returns. We have a few options: - Keep...
How are users expected to encode 'enumerated' values in OpenTelemetry? Could be a gauge w/ string value? We need to figure this out.
There are circumstances for instrumented actions where: 1. The action is frequent and of low interest: a healthcheck, polling a message queue, etc. 2. An OpenTracing exporter uses libraries that...
The metric semantic conventions has the following [instrument naming](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/metrics/semantic_conventions#instrument-naming) recommendation: > limit - an instrument that measures the constant, known total amount of something should be called entity.limit. For example,...
Several months ago the [OTEP](https://github.com/open-telemetry/oteps/blob/main/text/trace/0174-http-semantic-conventions.md) that captures the scope and roadmap for HTTP semantic conventions v1.0 (along with the scope for vNext) was reviewed and merged (https://github.com/open-telemetry/oteps/pull/174). It was actively...
**What are you trying to achieve?** I'm currently working on the micrometer->OTel bridge instrumentation in the javaagent. Micrometer offers the possibility to remove a meter from the `MeterRegistry` and stop...
Consider these canonical examples: Span Name | Guidance -- | -- get_account | Good, and account_id=42 would make a nice Span attribute get_account/{accountId} | Also good (using the "HTTP route")...
### Discussed in https://github.com/open-telemetry/opentelemetry-specification/discussions/2539 Originally posted by **FWinkler79** May 13, 2022 Hi there, I have a question concerning the naming conventions of custom attributes that - as of today -...
See https://github.com/open-telemetry/opentelemetry-specification/pull/263#issuecomment-544441748 and https://github.com/open-telemetry/opentelemetry-specification/pull/263#discussion_r329281769. We should find a way to represent information about the HTTP application (proposed name semantic attribute name `http.app`) *somewhere*, ideally somewhere where for each incoming HTTP...
We don't yet have a guideline regarding how language SIGs should sign the binaries that they release. We're seeing asks from multiple SIGs: * https://github.com/open-telemetry/opentelemetry-dotnet/issues/1302 * https://github.com/open-telemetry/opentelemetry-collector/issues/5254 A possible solution...
