Modern Kubernetes environments are dynamic and complex, often comprising hundreds or thousands of ephemeral services and workloads. While Kubernetes-native observability tools provide some visibility, developers and operators frequently lack the contextual insights necessary to correlate service performance with infrastructure events, deployment changes, or network bottlenecks.
Today, we’re announcing the preview release of Kubernetes Monitoring with OpenTelemetry—a significant step forward in open, scalable, and frictionless observability for cloud-native environments.
This new capability combines OpenTelemetry Collector metrics, events and logs with Kubernetes metadata in a single, curated New Relic experience. It enables teams to quickly diagnose performance anomalies across pods, services, nodes, and namespaces without writing a single line of instrumentation code.
Kubernetes Monitoring with OpenTelemetry helps improve detection, troubleshooting, and collaboration across DevOps, SRE, and platform teams—without requiring the installation of additional agents or custom exporters and with an unified view, you no longer need to piece together disparate views from Grafana, kubectl, and CloudWatch.
Key capabilities include:
- Zero-Code, OpenTelemetry-Native Instrumentation: Automatically collects pod, node, and container metrics/logs with OpenTelemetry Collector—no manual setup required.
- Unified Observability in One Place: Correlate logs, metrics, events and metadata (CPU, memory, pod name, etc.) across your Kubernetes workloads—no need to jump between kubectl, CloudWatch, or Grafana.
- Faster Troubleshooting with Curated Dashboards: Instantly visualize container health, pod restarts, alert status, and more—plus, drill into related APM services and logs without context-switching.
- Future-proof your observability investment: Built on OpenTelemetry and Prometheus to ensure flexibility and avoid vendor lock-in with Open Standards.
- Enterprise-Grade OTel Scalability: Handles high-cardinality data at scale with cost-efficient processing—perfect for large clusters, multi-tenant setups, and modern CI/CD workflows.
How to Get Started
You can get started with just a few steps:
- Install the OpenTelemetry Collector on your Kubernetes cluster.
- Use the New Relic Helm chart to deploy the Kubernetes monitoring pipeline.
- Configure your license key and cluster name in the Helm values file.
- Select Kubernetes dashboards in New Relic under APM & Services > Kubernetes Monitoring.
Next steps
Ready to reduce blind spots in your Kubernetes environment?
Try Kubernetes Monitoring with OpenTelemetry now in preview:
Read the documentation →
Don’t have New Relic yet? Sign up for free and — includes 100 GB/month of free data ingest, unlimited free basic users, and immediate access to New Relic’s Open Telemetry tool for Kubernetes Monitoring.
The views expressed on this blog are those of the author and do not necessarily reflect the views of New Relic. Any solutions offered by the author are environment-specific and not part of the commercial solutions or support offered by New Relic. Please join us exclusively at the Explorers Hub (discuss.newrelic.com) for questions and support related to this blog post. This blog may contain links to content on third-party sites. By providing such links, New Relic does not adopt, guarantee, approve or endorse the information, views or products available on such sites.
