Skip to main content
Use OpenTelemetry to collect Kubernetes resource and status metrics from nodes, pods, containers, and volumes. This data answers questions like:
  • Which pods are using the most CPU?
  • How do resource limits compare to container resource use?
  • What do system metrics look like at the node level?
  • Why are pods failing to start?
Adding telemetry to Kubernetes and then analyzing with Honeycomb provides a flexible way to aggregate, structure, and enrich events from applications running on Kubernetes. This data answers questions like:
  • How did response time change after a canary deployment?
  • How does application performance vary with container resource limits?
  • Are application errors happening on specific nodes, or across the fleet?

​
Getting Started: Create Your Telemetry Pipeline

Do you have 10 minutes? Then you’ve come to the right place. Use our Quick Start to create a telemetry pipeline, which will prepare you to instrument your application code.

Create a Telemetry Pipeline

Use Helm to deploy OpenTelemetry Collectors that set up a telemetry pipeline to send Kubernetes metrics and events from your cluster to Honeycomb.

​
Add Low-Code Automatic Instrumentation to Your Applications

Once you have a telemetry pipeline in place, add automatic instrumentation to your applications.
If you have already used OpenTelemetry to instrument your applications to send data to Honeycomb, you can skip this step and jump straight to configuring OpenTelemetry to forward telemetry data to your Collectors.

OpenTelemetry Operator for Kubernetes

Set up the OpenTelemetry Operator for Kubernetes to add automatic instrumentation to your applications—using very little code.

​
Getting Help

To ask questions and learn more, join our Pollinators Community Slack.