OpenTelemetry in 2026: Finally Ready for Production?

We’ve been cautiously watching OpenTelemetry since 2022. The promise was compelling: a vendor-neutral, open standard for collecting telemetry data — traces, metrics, logs — from your applications. The reality was rough edges, incomplete language support, and performance overhead that made us hesitant to commit.

In August 2025, we finally made the move. Six months in, here’s the honest assessment.

What Works Well

Auto-instrumentation is genuinely impressive now. For Python and Go applications, you can get distributed tracing with zero code changes for most frameworks. The collector pipeline is flexible and powerful — fan out to multiple backends, transform data, sample intelligently. The ecosystem of compatible backends has matured dramatically.

What’s Still Rough

The logs specification is the weakest link. Trace and metrics are solid; logs correlation is functional but not seamless. The cardinality problem on metrics is real and requires careful attribute selection to avoid cost explosions in your backend. And the documentation, while improved, still has significant gaps for complex configurations.

Our Verdict

Yes, production-ready — with caveats. If you’re starting a new observability stack, OTel is the right foundation. If you’re migrating from a mature proprietary setup, budget more time than you think you need and start with one service before going wide.