Hi, in the case of "process up but not working" which can be considered a particular case, I would setup a custom script (Bash? Python?) and use Nagios/Icinga for the alerting
For the collection of the metrics, I would connect Collectd to JMX, and then link Collectd directly on Grafana (http://grafana.org/). The usual annoying part is to build the Collectd configuration for the interested MBeans; but probably someone has done this already I also would be interested in a generic good practice to query JMX, since I didn't find a human way to do it using Python or Ruby .. Simone Roselli ITE Sysadmin [email protected] http://www.plista.com ----- Original Message ----- From: "Guillermo Ortiz" <[email protected]> To: "user" <[email protected]> Sent: Thursday, January 21, 2016 11:54:34 AM Subject: Monitoring Flume Hello, I've looking for solutions to monitor a Flume Agent. Sometimes the process is running but it isn't available to process any message because some error happened. So, the process is running but Flume doesn't work. How are people monitoring Flume in general? We thought to create a JMX Source and send all data to some sink and do the monitoring based on the JMX logs though Solr or whatever. Any other solution or advise about monitoring Flume?
