We want to deprecate check_ganglia in favor of check_graphite. Both Hadoop and Kafka still have monitoring::ganglia uses.
Description
Details
Related Objects
Event Timeline
We removed a bunch of monitoring::ganglia usages as part of the Kafka upgrade and expansion. The only one that is currently left for analytics use is monitoring::ganglia { 'hadoop-hdfs-namenode-primary-is-active':
Change 244248 had a related patch set uploaded (by Ottomata):
Add statsd param to hadoop jmxtrans classes
Change 244249 had a related patch set uploaded (by Ottomata):
Configure hadoop master and worker to send jmx stats to statsd
Change 244249 merged by Ottomata:
Configure hadoop master and worker to send jmx stats to statsd
Change 244456 had a related patch set uploaded (by Ottomata):
Add script for icinga checks of hdfs active namenode
Change 244456 merged by Ottomata:
Add script for icinga checks of hdfs active namenode
This is really just curiosity and not a rhetorical question. What is better about monitoring::graphite vs. monitoring:;ganglia?
Change 244457 had a related patch set uploaded (by Ottomata):
Update cdh module with check_hdfs_active_namenode script, set up nrpe monitoring
Change 244457 merged by Ottomata:
Update cdh module with check_hdfs_active_namenode script, set up nrpe monitoring
Change 244460 had a related patch set uploaded (by Ottomata):
Allow nagios user to sudo to hdfs to run check_hdfs_active_namenode
Change 244460 merged by Ottomata:
Allow nagios user to sudo to hdfs to run check_hdfs_active_namenode
Change 244482 had a related patch set uploaded (by Ottomata):
Remove monitoring::ganglia hadoop-hdfs-namenode-primary-is-active
Change 244482 merged by Ottomata:
Remove monitoring::ganglia hadoop-hdfs-namenode-primary-is-active
Change 244491 had a related patch set uploaded (by Ottomata):
Remove no longer used monitoring::ganglia 'hadoop-hdfs-namenode-primary-is-active'
Change 244491 merged by Ottomata:
Remove no longer used monitoring::ganglia 'hadoop-hdfs-namenode-primary-is-active'