Heapster
Heapster enables Container Cluster Monitoring and Performance Analysis.
Heapster currently supports Kubernetes and CoreOS natively. Heapster is compatible with kubernetes versions starting from v1.0.6 only
It can be extended to support other cluster management solutions easily.
Heapster collects and interprets various signals like compute resource usage, lifecycle events, etc, and exports cluster metrics via REST endpoints. Note: Some of the endpoints are only valid in Kubernetes clusters
Heapster supports multiple sources of data. More information here.
Heapster supports a pluggable storage backend. It supports InfluxDB with Grafana, Google Cloud Monitoring, ElasticSearch, Google Cloud Logging, Hawkular, Riemann and Kafka. We welcome patches that add additional storage backends. Documentation on storage sinks here The current version of Storage Schema is documented here.
Running Heapster on Kubernetes
To run Heapster on a Kubernetes cluster with,
- InfluxDB use this guide.
- Google Cloud Monitoring and Google Cloud Logging use this guide.
Running Heapster on OpenShift
Using Heapster to monitor an OpenShift cluster requires some additional changes to the Kubernetes instructions to allow communication between the Heapster instance and OpenShift's secured endpoints. To run standalone Heapster or a combination of Heapster and Hawkular-Metrics in OpenShift, follow this guide.
Troubleshooting guide here
Community
Contributions, questions, and comments are all welcomed and encouraged! minkube developers hang out on Slack in the #sig-instrumentation channel (get an invitation here). We also have the kubernetes-dev Google Groups mailing list. If you are posting to the list please prefix your subject with "heapster: ".