OpenTelemetry Achieves CNCF Graduation After Seven Years, Confirming Its Role as the De Facto Observability Standard
The CNCF announced OpenTelemetry's graduation on May 21, capping seven years of development and a merger of two rival projects into a unified observability standard with 12,000+ contributors.
Overview
The Cloud Native Computing Foundation (CNCF) announced on May 21, 2026 that OpenTelemetry has reached Graduated project status — the highest maturity level in the CNCF ecosystem. The milestone formalizes what practitioners have treated as fact for several years: OpenTelemetry is the industry’s default framework for collecting and exporting observability data.
The graduation announcement was made at the Observability Summit in Minneapolis. According to the CNCF projects page, the formal vote to move OpenTelemetry to Graduated status occurred on May 11, 2026, with the public announcement following ten days later.
What OpenTelemetry Is
OpenTelemetry is an open, vendor-neutral observability framework for cloud native software that standardizes the collection, processing, and exporting of telemetry data — specifically metrics, logs, and traces, according to DBTA. The project provides a unified set of APIs, SDKs, a Collector agent, and semantic conventions, meaning organizations can change their observability backend without re-instrumenting their applications.
Key technical components include the OpenTelemetry Collector, the OpenTelemetry Protocol (OTLP), the OpenTelemetry Operator, and the Kubernetes Attributes Processor, as detailed by Virtualization Review. All three major cloud platforms have native integration: Microsoft Azure supports OTLP ingestion via Azure Monitor, Azure Kubernetes Service, VMs, and Arc-enabled servers; AWS added native OpenTelemetry metrics to CloudWatch in April 2026 and supports EKS Container Insights; and Google Cloud integrates through Cloud Trace and Cloud Monitoring.
From Rival Projects to a Unified Standard
OpenTelemetry’s origins lie in a community split. The project was formed in 2019 through CNCF assistance as a merger between OpenTracing and OpenCensus — two competing frameworks for distributed tracing and metrics that had divided the observability ecosystem, per the CNCF announcement. The merger eliminated that fragmentation.
The CNCF accepted OpenTelemetry on May 7, 2019, moved it to Incubating status on August 26, 2021, and formally graduated it on May 11, 2026, according to the project’s official CNCF timeline.
Chris Aniszczyk, CTO of CNCF, described the scale of the project’s reach: “As organizations increasingly scale AI and cloud native workloads, real time observability is critical for operational success. OpenTelemetry’s graduation solidifies it as the essential, unified observability standard, providing the consistent visibility required to understand and oversee complex systems,” as quoted by DBTA. In a separate remark reported by The Stack, Aniszczyk characterized the project as having “essentially become the kubernetes of the observability world.”
Scale and Adoption
The project has attracted over 12,000 contributors from more than 2,800 companies, with hundreds of maintainers organized across language-specific Special Interest Groups, per the CNCF. The CNCF project metrics page puts the total contributor count at 28,351, representing a 7% year-over-year increase, across 5,536 contributing organizations.
Download numbers reflect widespread production use. Over the past twelve months, the OpenTelemetry JavaScript API package was downloaded more than 1.36 billion times and the Python API package surpassed 1.3 billion downloads; both packages set new monthly records in April 2026, according to the CNCF.
Among the organizations listed as adopters in the CNCF announcement are Alibaba, Anthropic, Bloomberg, Capital One, eBay, FICO Software, and Heroku. The project has achieved the second-highest velocity among over 240 CNCF projects — second only to Kubernetes.
Austin Parker, a member of the OpenTelemetry Governance Committee and Director of AI Strategy at honeycomb.io, attributed the milestone to sustained cross-organizational effort: “OpenTelemetry’s graduation is the result of decades of collective effort from individuals, companies, and cloud native practitioners to make observability a built-in part of software,” per DBTA.
What Graduation Required
To reach Graduated status, OpenTelemetry completed a third-party independent security audit for core components including the OpenTelemetry Collector, passed a formal governance review confirming project maturity, and incorporated community feedback on production readiness, as listed by DBTA.
Recent development activity includes the addition of Kotlin as a supported language and the promotion of the Profiles signal to alpha stage.
What We Don’t Know
The CNCF announcement does not specify which individual companies contributed the most code or maintainer hours. The CNCF project metrics show that while contributor counts rose 7% year-over-year, the number of contributing organizations declined 5%, which may reflect consolidation of contribution among existing participants rather than entirely new organizational entrants.
It is also not clear how quickly the Profiles signal will advance beyond alpha, or when Kotlin SDK support will be considered production-ready.
What Comes Next
The OpenTelemetry community stated that graduation marks a milestone rather than a destination. The project’s official blog noted: “Graduation is not the finish line. The OpenTelemetry community remains committed to building interoperable, high-quality observability standards and tooling for cloud native software at global scale.”