mirror of https://github.com/k3s-io/k3s
41 lines
2.5 KiB
Markdown
41 lines
2.5 KiB
Markdown
|
# Heapster
|
||
|
|
|
||
|
|
[](https://godoc.org/k8s.io/heapster) [](https://travis-ci.org/kubernetes/heapster)
|
||
|
|
|
||
|
|
Heapster enables Container Cluster Monitoring and Performance Analysis.
|
||
|
|
|
||
|
|
Heapster currently supports [Kubernetes](https://github.com/kubernetes/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](docs/model.md).
|
||
|
|
**Note: Some of the endpoints are only valid in Kubernetes clusters**
|
||
|
|
|
||
|
|
Use [Kubedash](https://github.com/kubernetes/kubedash) to visualize data exported by Heapster.
|
||
|
|
|
||
|
|
Heapster supports multiple sources of data.
|
||
|
|
More information [here](docs/source-configuration.md).
|
||
|
|
|
||
|
|
Heapster supports a pluggable storage backend.
|
||
|
|
It supports [InfluxDB](http://influxdb.com) with [Grafana](http://grafana.org/docs/features/influxdb), [Google Cloud Monitoring](https://cloud.google.com/monitoring/), [Google Cloud Logging](https://cloud.google.com/logging/), [Hawkular](http://www.hawkular.org), [Riemann](http://riemann.io) and [Kafka](http://kafka.apache.org/).
|
||
|
|
We welcome patches that add additional storage backends.
|
||
|
|
Documentation on storage sinks [here](docs/sink-configuration.md)
|
||
|
|
The current version of Storage Schema is documented [here](docs/storage-schema.md).
|
||
|
|
|
||
|
|
### Running Heapster on Kubernetes
|
||
|
|
|
||
|
|
To run Heapster on a Kubernetes cluster with,
|
||
|
|
- InfluxDB use [this guide](docs/influxdb.md).
|
||
|
|
- Google Cloud Monitoring and Google Cloud Logging use [this guide](docs/google.md).
|
||
|
|
|
||
|
|
### 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](https://github.com/openshift/origin-metrics).
|
||
|
|
|
||
|
|
#### Troubleshooting guide [here](docs/debugging.md)
|
||
|
|
|
||
|
|
### Community
|
||
|
|
|
||
|
|
Contributions, questions, and comments are all welcomed and encouraged! Heapster and cAdvisor developers hang out in the [#google-containers](http://webchat.freenode.net/?channels=google-containers) room on freenode.net. You can also reach us on the [google-containers Google Groups mailing list](https://groups.google.com/forum/#!forum/google-containers).
|