Skip to main content
Hello OpenTelemetry users — this lesson reviews the OpenTelemetry specification status and the lifecycle used to communicate maturity and stability for components and signals. Understanding component maturity helps set expectations for design, support, and production readiness. Below is a concise lifecycle definition followed by the official status summary for common signals.

​
OpenTelemetry component lifecycle

StageWhat it means
DraftDesign phase. Not yet part of the specification; requirements and APIs are still evolving.
ExperimentalReleased for community testing. Use to validate design and provide feedback; not guaranteed stable or backward-compatible.
StableBackward compatible and production-ready. Includes long-term support expectations.
DeprecatedStable for a transition period but scheduled for removal; users should plan migration paths.
The image illustrates the OpenTelemetry Component Lifecycle, showing four stages: Draft, Experimental, Stable, and Deprecated. Each stage is described with its current status and purpose in the lifecycle.
The specification status pages evolve over time. Check the official OpenTelemetry specs/status pages (OpenTelemetry specification repository) for the latest maturity indicators before making production decisions.

​
Official status summary (signals and components)

The OpenTelemetry specification provides a status summary table for each signal across these components: API, SDK, OTLP protocol, and Collector. The table below condenses the current maturity snapshot for common signals. This helps teams decide which parts are safe to rely on in production and which are still maturing.
Signal / ComponentAPISDKOTLP protocolCollector
TracingStableStableStableStable
MetricsStableMixed (some evolving features)StableMostly production-ready; some pipelines remain experimental
LogsStable (Bridge API)StableStableSupported
BaggageStable (feature freeze)StableNot applicableNot applicable
ProfilingExperimental / MaturingExperimental / MaturingExperimental / MaturingExploring collection and instrumentation support
The image is a summary table showing the status of various OpenTelemetry signal components, including API, SDK, OTLP protocol, and Collector, across different signals like tracing, metrics, logs, baggage, and profile. Each component is marked as stable, mixed, experimental, or with other relevant status descriptions.
Profiling remains early-stage: APIs, SDKs, and protocol definitions are still maturing, and the Collector is experimenting with continuous profiling features and related instrumentation/collection workflows.

​
How to use this information

  • Prefer Stable components for production workloads (e.g., tracing).
  • Use Experimental components with caution and for testing or evaluation purposes.
  • Track deprecation notices and migration guidance for components marked Deprecated.
  • Consult the canonical status table in the specification repository before adopting or upgrading components.
Links and references That’s it for this lesson.

Watch Video