Heapster enables Container Cluster Monitoring.

Internally, heapster uses cAdvisor for compute resource usage metrics.

Heapster currently supports Kubernetes and CoreOS natively. It can be extended to support other cluster management solutions easily. While running in a Kube cluster, heapster collects compute resource usage of all pods and nodes.

Source configuration is documented here.

Heapster supports a pluggable storage backend. It supports InfluxDB with Grafana, Google Cloud Monitoring and Google Cloud Logging. We welcome patches that add additional storage backends.

To run Heapster on a Kubernetes cluster with,

• InfluxDB use this guide.
• Google Cloud Monitoring and Google Cloud Logging use this guide.

Take a look at the storage schema here.

When Heapster is running on a Kubernetes cluster, the Heapster Model can be used to extract aggregated metrics and derived stats for various Kubernetes cluster entities.

Heapster communicates with the local fleet server to get cluster information. It expected cAdvisor to be running on all the nodes. Refer to this guide.

Heapster can be used to enable cluster-wide monitoring on other cluster management solutions by running a simple cluster-specific buddy container that will help Heapster with discovery of hosts.

It is also possible to run Heapster standalone on a host with cAdvisor using this guide.

Contributions, questions, and comments are all welcomed and encouraged! Heapster and cAdvisor developers hang out in the #google-containers room on freenode.net. You can also reach us on the google-containers Google Groups mailing list.