Moving Beyond “Supports OpenTelemetry”: Why There’s a Need for a Shared Maturity Model

OpenTelemetry has transitioned from an experimental integration to a core component of modern cloud-native infrastructure, as evidenced by its widespread adoption among organizations surveyed by the CNCF. This shift reflects a broader movement towards open standards and vendor-neutral platforms, emphasizing the importance of structured telemetry for comprehensive system observability. Automatic instrumentation provides a quick start, but the real value lies in native instrumentation, which ensures meaningful context and semantics across critical infrastructure components. The challenge lies in maintaining consistent and coherent telemetry, as the traditional "three pillars" of logs, metrics, and traces need to be correlated for effective system understanding. The proposal of an OpenTelemetry Support Maturity Model aims to provide a nuanced framework for evaluating integration quality across multiple dimensions, moving beyond the binary "supports OpenTelemetry" label to better guide architectural decisions and foster trust in shared observability infrastructure. This approach seeks to improve clarity and alignment among project maintainers, platform engineers, and end users, ensuring that telemetry integration evolves in a way that supports robust system-level insight and operational readiness.