Kubernetes environments generate a constant stream of signals across clusters, nodes, pods, and workloads. For teams that have standardized on OpenTelemetry (OTel), maintaining ownership of that data is critical. But in practice, many observability platforms require translation into vendor-specific data formats, leading to fragmented product experiences, blank dashboards, and uncertainty about data integrity.
Today, we’re announcing a Preview of native OTel support in the Datadog Kubernetes Explorer. Building on our existing support for OTel metrics, this expansion brings first-class, in-app Kubernetes exploration and troubleshooting powered directly by your OTel data. You can now visualize clusters, investigate resource health, and correlate metrics, logs, and traces without sacrificing vendor flexibility or data ownership.
In this post, we’ll show you how to:
Resolve variations in OTel Kubernetes metric types and semanticsCorrelate OTel metrics and alerting signals in the Kubernetes ExplorerUnderstand cluster root causes and related resources by using OTel data
Resolve variations in OTel Kubernetes metric types and semantics
