Specification documents (files) may explicitly define a “Status”, typically shown immediately after the document title. When present, the “Status” applies to the individual document only and not to the entire specification or any other documents. The following table describes what the statuses mean. Maturity levels The support guarantees and allowed changes are governed by the maturity level of the document. Maturity levels are defined in OTEP 0232 and follow the OpenTelemetry project...| OpenTelemetry
Status: Mixed Users of OpenTelemetry need a way for instrumentation interactions with the OpenTelemetry API to actually produce telemetry. The OpenTelemetry SDK (henceforth referred to as the SDK) is an implementation of the OpenTelemetry API that provides users with this functionally. All language implementations of OpenTelemetry MUST provide an SDK. MeterProvider Status: Stable A MeterProvider MUST provide a way to allow a Resource to be specified. If a Resource is specified, it SHOULD be a...| OpenTelemetry
This document defines some terms that are used across this specification. Some other fundamental terms are documented in the overview document. User Roles Application Owner The maintainer of an application or service, responsible for configuring and managing the lifecycle of the OpenTelemetry SDK. Library Author The maintainer of a shared library which is depended upon by many applications, and targeted by OpenTelemetry instrumentation. Instrumentation Author The maintainer of OpenTelemetry i...| OpenTelemetry
Status: Mixed Overview Status: Stable The OpenTelemetry data model for metrics consists of a protocol specification and semantic conventions for delivery of pre-aggregated metric timeseries data. The data model is designed for importing data from existing systems and exporting data into existing systems, as well as to support internal OpenTelemetry use-cases for generating Metrics from streams of Spans or Logs. Popular existing metrics data formats can be unambiguously translated into the Ope...| OpenTelemetry
Status: Stable Attribute An Attribute is a key-value pair, which MUST have the following properties: The attribute key MUST be a non-null and non-empty string. Case sensitivity of keys is preserved. Keys that differ in casing are treated as distinct keys. The attribute value is either: A primitive type: string, boolean, double precision floating point (IEEE 754-1985) or signed 64 bit integer. An array of primitive type values. The array MUST be homogeneous, i.| OpenTelemetry
This document provides an overview of the OpenTelemetry project and defines important fundamental terms. Additional term definitions can be found in the glossary. OpenTelemetry Client Architecture At the highest architectural level, OpenTelemetry clients are organized into signals. Each signal provides a specialized form of observability. For example, tracing, metrics, and baggage are three separate signals. Signals share a common subsystem – context propagation – but they function indepe...| OpenTelemetry