Cloudera Manager Metrics
This section provides information on metrics supported by Cloudera Manager.
A metric is a property that can be measured to quantify the state of an entity or activity. They include properties such as the number of open file descriptors or CPU utilization percentage across your cluster.
Cloudera Manager monitors a number of performance metrics for services and role instances running on your clusters. These metrics are monitored against configurable thresholds and can be used to indicate whether a host is functioning as expected or not. You can view these metrics in the Cloudera Manager Admin Console which displays metrics about your jobs (such as the number of currently running jobs and their CPU/memory usage), Hadoop services (such as the average HDFS I/O latency and number of concurrent jobs), your clusters (such as average CPU load across all your hosts) and so on.
You can disable collection of metrics for specific services, roles, and role groups. This can help to improve performance of the Cloudera Manager Service Monitor in large deployments. See Disabling Metrics for Specific Roles.
Cloudera Manager pre-aggregates metrics from their generating entity to the entities that they are part of. For example, metrics generated by disks, network interfaces, and filesystems are aggregated to their respective hosts and clusters. See Metric Aggregation for more details.
- List of metrics:
- Select .
- Click the question mark icon to the right of the Build Chart button.
- Click the List of Metrics link.
- Use the tsquery language to retrieve all metrics for the type of entity you are interested in. The tsquery language is the language used to specify statements for retrieving time series data, that is, a stream of metric data points with each point containing a timestamp and the value of the metric at that timestamp.
You can chart metrics over a time range. See Viewing Charts for Cluster, Service, Role, and Host Instances for more details. The metrics listed in this guide include a short description as well as their units and the version of CDH they are applicable to. Most of the units are self-explanatory. The unit "CPU seconds per second" is defined as the number of CPU seconds being used per second. For example, if you have a 1 host cluster with 16 cores, and 16 tasks each using one core, the value of the metric would be 16.
The sampling rate for all metrics is one minute.
Categories of Metrics:
- Accumulo Metrics
- Accumulo 1.4 Metrics
- Active Database Metrics
- Active Key Trustee Server Metrics
- Activity Metrics
- Activity Monitor Metrics
- Agent Metrics
- Alert Publisher Metrics
- Attempt Metrics
- Beeswax Server Metrics
- Cloudera Management Service Metrics
- Cloudera Manager Server Metrics
- Cluster Metrics
- DataNode Metrics
- Directory Metrics
- Disk Metrics
- Event Server Metrics
- Failover Controller Metrics
- Filesystem Metrics
- Flume Metrics
- Flume Channel Metrics
- Flume Sink Metrics
- Flume Source Metrics
- Garbage Collector Metrics
- HBase Metrics
- HBase REST Server Metrics
- HBase RegionServer Replication Peer Metrics
- HBase Thrift Server Metrics
- HDFS Metrics
- HDFS Cache Directive Metrics
- HDFS Cache Pool Metrics
- HRegion Metrics
- HTable Metrics
- History Server Metrics
- Hive Metrics
- Hive Metastore Server Metrics
- HiveServer2 Metrics
- Host Metrics
- Host Monitor Metrics
- HttpFS Metrics
- Hue Metrics
- Hue Server Metrics
- Impala Metrics
- Impala Catalog Server Metrics
- Impala Daemon Metrics
- Impala Daemon Resource Pool Metrics
- Impala Llama ApplicationMaster Metrics
- Impala Pool Metrics
- Impala Pool User Metrics
- Impala Query Metrics
- Impala StateStore Metrics
- Isilon Metrics
- Java KeyStore KMS Metrics
- JobHistory Server Metrics
- JobTracker Metrics
- JournalNode Metrics
- Kafka Metrics
- Kafka Broker Metrics
- Kafka Broker Topic Metrics
- Kafka MirrorMaker Metrics
- Kafka Replica Metrics
- Kerberos Ticket Renewer Metrics
- Key Management Server Metrics
- Key Management Server Proxy Metrics
- Key Trustee KMS Metrics
- Key Trustee Server Metrics
- Key-Value Store Indexer Metrics
- Kudu Metrics
- Kudu Replica Metrics
- Lily HBase Indexer Metrics
- Load Balancer Metrics
- Logger Metrics
- MapReduce Metrics
- Master Metrics
- Monitor Metrics
- NFS Gateway Metrics
- NameNode Metrics
- Navigator Audit Server Metrics
- Navigator HSM KMS Metastore Metrics
- Navigator HSM KMS Proxy Metrics
- Navigator HSM KMS backed by SafeNet Luna HSM Metrics
- Navigator HSM KMS backed by Thales HSM Metrics
- Navigator Metadata Server Metrics
- Network Interface Metrics
- NodeManager Metrics
- Oozie Metrics
- Oozie Server Metrics
- Passive Database Metrics
- Passive Key Trustee Server Metrics
- RegionServer Metrics
- Reports Manager Metrics
- ResourceManager Metrics
- SecondaryNameNode Metrics
- Sentry Metrics
- Sentry Server Metrics
- Server Metrics
- Service Monitor Metrics
- Solr Metrics
- Solr Replica Metrics
- Solr Server Metrics
- Solr Shard Metrics
- Spark Metrics
- Spark (Standalone) Metrics
- Spark 2 Metrics
- Sqoop 1 Client Metrics
- Sqoop 2 Metrics
- Sqoop 2 Server Metrics
- Tablet Server Metrics
- TaskTracker Metrics
- Telemetry Publisher Metrics
- Time Series Table Metrics
- Tracer Metrics
- User Metrics
- WebHCat Server Metrics
- Worker Metrics
- YARN (MR2 Included) Metrics
- YARN Pool Metrics
- YARN Pool User Metrics
- ZooKeeper Metrics
- Disabling Metrics for Specific Roles