In addition to these base metrics, many aggregate metrics are available. If an entity type has parents defined, you can formulate all possible aggregate metrics using the formula base_metric_across_parents.
In addition, metrics for aggregate totals can be formed by adding the prefix total_ to the front of the metric name.
Use the type-ahead feature in the Cloudera Manager chart browser to find the exact aggregate metric name, in case the plural form does not end in "s".
For example, the following metric names may be valid for HTable:
Some metrics, such as alerts_rate, apply to nearly every metric context. Others only apply to a certain service or role.
|Metric Name||Description||Unit||Parents||CDH Version|
|regions||Regions||regions||cluster, hbase, hnamespace||CDH 4, CDH 5|
|regions_healthy||The number of healthy regions in the table scanned by the HBase region health canary||regions||cluster, hbase, hnamespace||CDH 4, CDH 5|
|regions_slow_to_respond||The number of slow to respond regions in the table scanned by the HBase region health canary||regions||cluster, hbase, hnamespace||CDH 4, CDH 5|
|regions_with_errors||The number of regions in the table reporting errors when scanned by the HBase region health canary||regions||cluster, hbase, hnamespace||CDH 4, CDH 5|
|raw_size||This is the total physical disk space used by the HBase table including the replication factor. For the default replication factor of three, this is expected to be three times the size of all the table's store files.||bytes||cluster, hbase, hnamespace||CDH 5|