Kubernetes and Honeycomb | Honeycomb

Kubernetes and Honeycomb

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?

Go further and 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 does container resource use compare to limits? -What do system metrics look like at the node level?
  • Why are pods failing to start?

How to Instrument 

For any new observability efforts, we recommend instrumenting with OpenTelemetry with its benefits of broader support and richer instrumentation. To add tracing to your Kubernetes cluster, we recommend using the OpenTelemetry Collector with the OpenTelemetry Operator for Kubernetes.

Existing Honeycomb users may be using the Honeycomb Kubernetes Agent. The Honeycomb Kubernetes Agent predates the OpenTelemetry Collector’s existence and facilitated the collection of logs and metrics from Kubernetes. Since its creation, the OpenTelemetry Collector has grown to be a primary solution for traces, metrics, and logs in Kubernetes.

Getting Help 

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