Answers about viewing Kubernetes metrics in Wavefront

The Wavefront Collector for Kubernetes on github enables monitoring Kubernetes clusters and sending metrics to Wavefront. Much of the doc for the project is in the docs folder on Github. This page has some special tips and tricks to help you create the user experience you’re after.

What is the Wavefront Collector for Kubernetes?

The Wavefront Collector is an agent that you deploy within a Kubernetes cluster as a DaemonSet.This agent collects metrics about a Kubernetes cluster and sends them to the Wavefront SaaS service. You can visualize these metrics using pre-built dashboards that help you monitor your Kubernetes clusters.

Do I Have to Deploy the Wavefront Collector on Every Kubernetes Cluster?

Yes, deploy Wavefront Collector on each of your Kubernetes clusters.

How Can I Filter Metric Data?

During the Helm installation, you can pass in a values.yaml as a parameter.

Using values.yaml you can:

How Do I Monitor Prometheus Metric Endpoints?

Many Kubernetes components and applications expose metrics in the Prometheus format via HTTP endpoints. The Wavefront Collector natively supports discovering such endpoints and collecting metrics from them. The Collector listens for the addition of pods within a Kubernetes cluster, and can automatically start collecting the prometheus metrics from pods by:

  • Adding specific annotations on a pod to inform the Collector to start collecting metrics from it.
  • Configuring static discovery rules to identify pods by labels, namespaces or image names and information on how to collect metrics from the pods.

See the auto discovery documentation for details.

The Wavefront Collector supports monitoring over 20 popular applications such as Redis, Memcached, Postgres, MongoDB etc. Use static discovery rules to monitor these applications.