The encyclopedia · Software & IT · Technical decision · 2019–2026
OpenTelemetry merged two rival APIs and became observability's de facto standard
In 2019 CNCF merged OpenTracing and OpenCensus into OpenTelemetry: one vendor-neutral API/SDK — instrument once, switch backends, now the de facto standard.
Cloud Native Computing Foundation (CNCF) · OpenTelemetry
The solution
By the late 2010s observability had split into two overlapping camps, OpenTracing and OpenCensus, each with its own APIs and SDKs. Choosing one meant betting on a community; supporting both meant instrumenting twice. In 2019 CNCF brokered a merger of the two projects into OpenTelemetry.
The merged project's promise was a single set of APIs, SDKs, a Collector agent and semantic conventions. Because the interfaces are vendor-neutral, an organization can switch its tracing or metrics backend without ripping out agents and re-instrumenting — the code stays put and only the export target changes.
Adoption compounded. By May 2026, when CNCF announced OpenTelemetry's graduation, the project had over 12,000 contributors from over 2,800 companies, the second-highest velocity of any project in the cloud-native ecosystem after Kubernetes, and JavaScript and Python API packages each downloaded more than a billion times in a year — CNCF called it the de facto observability standard.
Why it worked
- One vendor-neutral API means code is instrumented once, not per backend.
- Vendors compete on what they do with telemetry, not on locking it in.
- CNCF governance gave enterprises a neutral home to bet on.
- Metrics, logs and traces share one pipeline, cutting agent sprawl.
What can be applied
When the standard is vendor-neutral, every tool vendor can support it — teams adopt it once because it removes lock-in instead of adding it.
Aftermath
OpenTelemetry graduated from CNCF in May 2026, and the industry shifted from competing on who has the best telemetry to who does the most with the telemetry everybody has. Vendors from Datadog to Splunk now build their products around it, and it sits alongside Kubernetes as a default layer of the cloud-native stack.
Sources
- Cloud Native Computing Foundation Announces OpenTelemetry's Graduation, Solidifying Status as the De Facto Observability Standard
- OpenTelemetry Documentation
spotted an error? The archive wants to know.