opentelemetry-specification
opentelemetry-specification copied to clipboard
open-telemetry
Specifications for OpenTelemetry
when naming metric name and attribute name, what is the difference between **state** and **status**? in https://opentelemetry.io/docs/reference/specification/metrics/semantic_conventions/system-metrics/: system.cpu.time, **state**=idle, user, system, interrupt, etc. system.memory.usage, **state**=used, free, cached, etc. system.processes.count, **status**=running,...
**What are you trying to achieve?** Sending traces with different strategies What did you expect to see? toggle `sampled` value for processors configurable via envs/properties I think we can take...
I have a Node.JS app which uses module written in C++. I need to pass spans from one language to another, in both directions. I cannot pass parent span directly,...
Please define semantic conventions for SIP protocol. It is similar to HTTP protocol, so mostly it would be enough take existing [conventions for HTTP](https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/http/) and replace `http` with `sip`. One...
The OpenTelemetry documentation has the following statement at [Collector Getting Started](https://opentelemetry.io/docs/collector/getting-started/): > OpenTelemetry instrumentation libraries by default export their data assuming a locally running Collector is available. Based on [this...
The client-side SIG is working on adding the concept of sessions. Sessions correlate signals from the same client / user over a certain period of time. We have considered two...
I am looking into creating instrumentation in python that will propagate traces over SQS messages. I have begun looking into the [specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/messaging.md) and noticed that the context propagation way is...
Instrument [units](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#instrument-unit) MUST be ASCII strings. Instrument [descriptions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#instrument-description) MUST support [BMP (Unicode Plane 0)](https://en.wikipedia.org/wiki/Plane_(Unicode)#Basic_Multilingual_Plane), which is basically only the first three bytes of UTF-8. Both of these allow [control characters](https://en.wikipedia.org/wiki/Control_character)...
As a result of the discussion in April 19th SIG meeting, it was suggested that it would be useful for debugging purposes that the OTLP exporter add version information to...
**What are you trying to achieve?** [Attribute naming conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/common/attribute-naming.md#recommendations-for-opentelemetry-authors) specify that all names SHOULD be part of a namespace. However, for many of the collector database receivers this is usually...
