Kafka Replica 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 Kafka Replica:
- kafka_log_end_offset_across_clusters
- total_kafka_log_end_offset_across_clusters
Some metrics, such as alerts_rate, apply to nearly every metric context. Others only apply to a certain service or role.
For more information about metrics, see Cloudera Manager Metrics and Metric Aggregation.
| Metric Name | Description | Unit | Parents | CDH Version |
|---|---|---|---|---|
| kafka_log_end_offset | The offset of the next message that will be appended to the log | message.units.offset | cluster, kafka, kafka-kafka_broker, kafka_broker_topic, kafka_topic, rack | CDH 4, CDH 5 |
| kafka_log_start_offset | The earliest message offset in the log | message.units.offset | cluster, kafka, kafka-kafka_broker, kafka_broker_topic, kafka_topic, rack | CDH 4, CDH 5 |
| kafka_num_log_segments | The number of segments in the log | message.units.segments | cluster, kafka, kafka-kafka_broker, kafka_broker_topic, kafka_topic, rack | CDH 4, CDH 5 |
| kafka_size | The size of the log | bytes | cluster, kafka, kafka-kafka_broker, kafka_broker_topic, kafka_topic, rack | CDH 4, CDH 5 |