3 ms·
We support that use case, here's a guide: http://www.boxever.com/monitoring-your-machines-with-prometheus http://www.boxever.com/monitoring-your-machines-with-p
by bbrazil 12y ago
We support that use case, here's a guide: http://www.boxever.com/monitoring-your-machines-with-prometheus http://www.boxever.com/monitoring-your-machines-with-prometh...
- xfalcox 12y agoThanks from a fellow brazilian!
- wyldfire 12y agoThat's great! > For machine monitoring Prometheus offers the Node exporter Is it possible for the frontend to utilize data from the cron-invoked sar/sadc that already covers much of this data? http://sebastien.godard.pagesperso-orange.fr/ http://sebastien.godard.pagesperso-orange.fr/
- bbrazil 12y agoThe default instrumentation that comes with node_exporter covers far more than what systat provides. Retrieving data from /proc at every scrape also gives you a more accurate timestamp, which helps reduce graph artifacts. As an aside, if you have machine-level cronjobs you want to expose metrics from you can use the textfile[1] module of the node_exporter, which reads in data from *.prom files in the same format as accepted by the Pushgateway. [1]https://github.com/prometheus/node_exporter/blob/master/collector/textfile.go https://github.com/prometheus/node_exporter/blob/master/coll... [2]https://github.com/prometheus/pushgateway https://github.com/prometheus/pushgateway