Impala Pool User Metrics

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 Impala Pool User:

• queries_ingested_rate_across_clusters
• total_queries_ingested_rate_across_clusters

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
queries_ingested_rate	Impala queries ingested by the Service Monitor	queries per second	cluster, impala, impala_pool	CDH 5, CDH 6, CDH 7
queries_oom_rate	Impala queries for which memory consumption exceeded what was allowed	queries per second	cluster, impala, impala_pool	CDH 5, CDH 6, CDH 7
queries_rejected_rate	Impala queries rejected from admission, commonly due to the queue being full or insufficient memory	queries per second	cluster, impala, impala_pool	CDH 5, CDH 6, CDH 7
queries_spilled_memory_rate	Impala queries that spilled to disk	queries per second	cluster, impala, impala_pool	CDH 5, CDH 6, CDH 7
queries_successful_rate	Impala queries that ran to completion successfully	queries per second	cluster, impala, impala_pool	CDH 5, CDH 6, CDH 7
queries_timed_out_rate	Impala queries that timed out waiting in queue during admission	queries per second	cluster, impala, impala_pool	CDH 5, CDH 6, CDH 7