This is the documentation for Cloudera Enterprise 5.8.x. Documentation for other versions is available at Cloudera Documentation.

Exposing HBase Metrics to a Ganglia Server

Ganglia is a popular open-source monitoring framework. You can expose HBase metrics to a Ganglia instance so that Ganglia can detect potential problems with your HBase cluster.

Expose HBase Metrics to Ganglia Using Cloudera Manager

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

  1. Go to the HBase service.
  2. Click the Configuration tab.
  3. Select the HBase Master or RegionServer role. To monitor both, configure each role as described in the rest of the procedure.
  4. Select Category > Metrics.
  5. Locate the Hadoop Metrics2 Advanced Configuration Snippet (Safety Valve) property or search for it by typing its name in the Search box.
  6. Edit the property. Add the following, substituting the server information with your own. 
    hbase.sink.ganglia.class=org.apache.hadoop.metrics2.sink.ganglia.GangliaSink31
hbase.sink.ganglia.servers=<Ganglia server>:<port>
hbase.sink.ganglia.period=10

    If more than one role group applies to this configuration, edit the value for the appropriate role group. See Modifying Configuration Properties Using Cloudera Manager.

  7. Click Save Changes to commit the changes.
  8. Restart the role.
  9. Restart the service.

Expose HBase Metrics to Ganglia Using the Command Line

  Important:
  • If you use Cloudera Manager, do not use these command-line instructions.
  • This information applies specifically to CDH 5.8.x. If you use a lower version of CDH, see the documentation for that version located at Cloudera Documentation.
  1. Edit /etc/hbase/conf/hadoop-metrics2-hbase.properties on the master or RegionServers you want to monitor, and add the following properties, substituting the server information with your own: 
    hbase.sink.ganglia.class=org.apache.hadoop.metrics2.sink.ganglia.GangliaSink31
hbase.sink.ganglia.servers=<Ganglia server>:<port>
hbase.sink.ganglia.period=10
  2. Restart the master or RegionServer.
Page generated July 8, 2016.