The Cloud Native Computing Foundation® (CNCF®), which builds sustainable ecosystems for cloud native software, announced the graduation of OpenTelemetry, a vendor-neutral, open source observability framework designed to standardize the collection, processing and exporting of telemetry data—specifically metrics, logs and traces.
“As organizations increasingly scale AI and cloud native workloads, real time observability is critical for operational success,” said Chris Aniszczyk, CTO, CNCF. “OpenTelemetry’s graduation solidifies it as the essential, unified observability standard, providing the consistent visibility required to understand and oversee complex systems. Since the project’s inception, it has been incredible to witness the sheer growth and adoption OpenTelemetry has had in the cloud native community and beyond. The project creators, maintainers and community members should all be proud of this milestone.”
Formed in 2019 through the assistance of CNCF as a merger between OpenTracing and OpenCensus, OpenTelemetry (OTel) was created to eliminate a community split between the two overlapping projects. This helped solve tool fragmentation by providing a single set of APIs, SDKs, Collector agent, and semantic conventions, thus allowing organizations to switch observability backends without re-instrumenting their entire codebase.
In the seven years since its creation, OpenTelemetry has achieved the second-highest project velocity among over 240 projects in the cloud native ecosystem, second only to Kubernetes, and is widely regarded as the “de facto” standard for open source observability. OpenTelemetry’s rise in CNCF’s project velocity underscores the project’s growth trajectory and how deeply the technology resonates with developers and end users. Today, the project has grown to include over 12,000 contributors from over 2,800 companies and hundreds of maintainers across various language-specific Special Interest Groups (SIGs).
“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,” said Austin Parker, OpenTelemetry governance committee and director of AI strategy, honeycomb.io. “When we launched this project, none of us expected that it would reach this level of popularity and impact. I’m incredibly thankful and indebted to our maintainers and contributors who helped get us to this point as well as the many individuals in the CNCF who have been a part of this journey.”
The project’s widespread adoption is gaining new interest as a layer to observe performance, reliability, accuracy and trustworthiness in AI workloads. In the past twelve months, the OpenTelemetry JavaScript API package was downloaded more than 1.36 billion times and the OpenTelemetry Python API package surpassed 1.3 billion downloads, with both API packages setting new monthly download records in April 2026. Organizations such as Alibaba, Anthropic, Bloomberg, Capital One, eBay, FICO Software, Heroku and others rely on OpenTelemetry to monitor and secure their systems.
OpenTelemetry continues to focus on its production readiness by recently adding support for new languages such as Kotlin and also promoting Profiles, now officially in alpha. It deeply integrates into the broader CNCF observability ecosystem and works alongside Kubernetes, Fluentd, Jaeger and Prometheus.
To officially achieve graduation, OpenTelemetry successfully engaged in a third-party independent security audit and reviews for core components such as the OpenTelemetry Collector, along with a formal governance review to confirm maturity. The project has also incorporated community feedback into updates to improve its production readiness.
Hot Topic
The Latest
Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...
As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...
For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...
I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...
Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...
80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...
40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...
Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...
Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...
Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...