Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time
December 1, 2022 10:18
March 28, 2022 11:04
November 23, 2022 09:35


Development of the Wavefront Collector for Kubernetes has moved to This repo is no longer maintained.

Wavefront Collector for Kubernetes

Go Report Card Docker Pulls

Wavefront is a high-performance streaming analytics platform for monitoring and optimizing your environment and applications.

The Wavefront Collector for Kubernetes is an agent that runs as a DaemonSet on each node within a Kubernetes cluster. It collects metrics and events about the cluster and sends them to the Wavefront SaaS service.


  • Collects real-time data from all layers of a Kubernetes environment
  • Multiple sources of metrics providing comprehensive insight:
  • Auto discovery of pods and services based on annotation and configuration
  • Daemonset mode for high scalability with leader election for monitoring cluster level resources
  • Rich filtering support
  • Auto reload of configuration changes
  • Internal metrics for tracking the collector health and configuration


Refer to the installation instructions.


The installation instructions use a default configuration suitable for most use cases. Refer to the documentation for details on all the configuration options.


Build using make and the provided Makefile.

Commonly used make options include:

  • fmt to go fmt all your code
  • tests to run all the unit tests
  • build that creates a local executable
  • container that uses a docker container to build for consistency and reproducability

Troubleshooting Dropped Metrics

Formerly, we would see the following error in the proxy logs when a metric has too many tags: Too many point tags. However, logic has been added to the collector to automatically drop tags in priority order to ensure that metrics make it through to the proxy and no longer cause this error. This is the order of the logic used to drop tags:

  1. Explicitly excluded tags (from tagExclude config). Refer here for an example scenario.
  2. Tags are empty or are interpreted to be empty ("tag.key": "", "tag.key": "-", or "tag.key": "/").
  3. Tags are explicitly excluded ("namespace_id": "...", "host_id": "...", "pod_id": "...", or "hostname": "...").
  4. Tag values are duplicated, and the shorter key is kept ("tag.key": "same value" is kept instead of "tag.super.long.key": "same value").
  5. Tag key matches alpha.* or beta.*, after keys have been sorted (e.g. "": "arm-group" or "": "amd64").
  6. (As a last resort) tag key matches IaaS-specific tags, after keys have been sorted ("": "agentpool", "": "us-central1-c", "": "arm-group", etc.).


Public contributions are always welcome. Please feel free to report issues or submit pull requests.