Implement an out-of-the-box monitoring solution about paz HOT 7 OPEN

@lukebond another option is to use collectd with the built-in cgroups monitoring and pump that data to statsd/graphite/influxdb. I'm playing with that now and should be able to give better feedback

from paz.

@lukebond it is early days, but I like statsd/influxdb/graphana a lot. influxdb was easy to install and easy to query.

from paz.

@twilson63 we just switched back to graphite from influxdb due to frustrations with querying... but I do think graphite is dead, influxdb just needs to catch up.

from paz.

+1 for Heapster, as per the link from readme
https://github.com/GoogleCloudPlatform/heapster/blob/master/docs/influxdb.md
it can target an Influx/Grafana setup
On 4 Mar 2015 03:57, "Ross Kukulinski" [email protected] wrote:

@twilson63 https://github.com/twilson63 we just switched back to
graphite from influxdb due to frustrations with querying... but I do think
graphite is dead, influxdb just needs to catch up.

—
Reply to this email directly or view it on GitHub
https://github.com/yldio/paz/issues/26#issuecomment-77093135.

from paz.

sounds like influxdb is agreed upon.

i like the way cAdvisor/heapster just automagically grabs data from Docker. not sure if statsd and collectd do that or if it will be more manual? if so my preference would go to heapster.

re graphite/grafana, is it an either/or thing, or both?

i'd like to settle on a decision here.

from paz.

Heapster is natively attuned to Docker's API, collectd requires a plugin or similar.

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

Guide here - it has images for cAdvisor, influx, heapster and grafana, which saves maintaining them in this project.

from paz.

for clarity, we're going with Heapster, InfluxDB and Grafana at this point

from paz.