The Moment Nobody Expected to Arrive This Fast
In November 2024, OpenTelemetry hit stable status for logs. That sentence might not land hard unless you’ve spent the last five years watching observability tooling splinter into incompatible fragments. What just happened is the completion of the trifecta: traces, metrics, and logs now live under a single open standard. The CNCF called it the most significant observability milestone since Prometheus. They’re not wrong.
I’ve been shipping metrics to half a dozen different backends over the course of my career. Each one felt like the right choice at the time. Each one locked you in just tight enough that switching felt like a rewrite. OpenTelemetry changes that calculus entirely. You instrument once. You send anywhere. This isn’t marketing copy. This is infrastructure finally maturing.
Production Is Already Here—Just Unevenly Distributed
Here’s what convinced me this wasn’t another aspirational open-source project: the Docker Hub numbers. The OpenTelemetry Collector has crossed 1 billion pulls. That’s top-10 territory on Docker Hub. Real infrastructure, real production workloads, real teams betting their observability on this thing.
A billion pulls doesn’t happen by accident. It doesn’t happen because marketing is good. It happens when engineers across thousands of companies collectively decide that this tool solves a real problem better than the alternatives. Those are your peers making this decision. Not once. Not as experiments. In production.
Grafana Labs surveyed 400 engineering organizations this year for their Grafana Labs Observability Survey 2025. Sixty-seven percent had adopted or were actively piloting OpenTelemetry instrumentation. Two years ago that number was forty-four percent. That’s adoption velocity you can’t ignore.
The Vendor Pressure Is Already Real
Datadog’s CFO went on a Q4 2024 earnings call and said something CFOs almost never say out loud: they acknowledged pricing pressure from open-source observability tooling. Specifically, they cited it as a factor in slower net revenue retention among SMB customers. That’s not speculation. That’s a public company admitting the game has changed.
This matters because CFOs don’t say things like this unless it’s undeniable. They have armies of lawyers and investor relations people ensuring every word is defensible. When Datadog says open-source tooling is pressure, what they mean is: we’re losing deals we used to win. SMBs are building on OpenTelemetry and deploying to open-source backends instead of calling us.
The pricing model that worked for a decade is breaking. If you’re paying per gigabyte ingested, and you can instrument with open standards and send to a cheap backend instead, the math becomes obvious. Vendors who built their model on capture and lock-in are discovering that lock-in requires friction. OpenTelemetry removes friction.
Multi-Cloud Becomes Real Without Vendor Code
Last year, AWS, Google Cloud, and Azure all announced native OTLP ingestion support. OTLP is the OpenTelemetry Line Protocol. What this means practically: you can instrument your code once and send it to any of these three platforms without writing a single line of cloud-specific code. Zero vendor SDKs. Zero lock-in mechanisms baked into your instrumentation layer.
This is the infrastructure equivalent of a standard shipping container. Before containers, shipping was vendor-specific. Shipping companies had their own boxes. Standards killed that. OTLP is doing the same thing to observability.
Try that five years ago. You’d instrument with Datadog’s SDK. You’d instrument with New Relic’s SDK. If you wanted to switch, you’d find instrumentation code scattered across your codebase. Now you instrument once with OpenTelemetry project official site libraries. You deploy to AWS today, Google Cloud next quarter, and your instrumentation doesn’t budge. It doesn’t know the difference.
What This Means for You Next
If you’re building new services, this is your path. If you’re maintaining instrumentation in an existing system, you don’t have to rip and replace today. But you should be thinking about it. Not because OpenTelemetry is perfect, because it’s not, but because it’s stable, widely adopted, and most importantly, it removes your observability stack as a reason to stay with a vendor.
The competitive game for observability is shifting from “who has the best visualization” to “who has the cheapest egress for OTLP data.” That’s a different game. Cheaper wins. Open wins. Boring infrastructure wins.
If you’ve been sitting with this on your backlog, now is the moment. Not next quarter. Now. The window where switching costs money is closing fast. The window where it costs nothing is opening. Have you already moved any services to OpenTelemetry? I’d like to hear what worked and what didn’t.