Kafka Broker Health Tests

Kafka Broker Audit Pipeline Test

This Kafka Broker health test checks that the Auditing for the Kafka Broker role is getting processed correctly and is not blocked. A failure of this health test may indicate a problem with the audit pipeline of Kafka Broker process. This test can fail either because the Cloudera Audit Server is not accepting audits, or the Cloudera Manager Agent on the Kafka Broker host isn't able to send audits because of some network issue. Check the Cloudera Manager Agent logs and Cloudera Audit Server logs for more details. This test can be enabled or disabled using the Navigator Audit Pipeline Health Check Kafka Broker monitoring setting.

Short Name: Audit Pipeline Test

Property Name Description Template Name Default Value Unit
Monitoring Period For Audit Failures The period to review when checking if audits are blocked and not getting processed. mgmt_navigator_failure_window 20 MINUTES
Navigator Audit Failure Thresholds The health test thresholds for failures encountered when monitoring audits within a recent period specified by the mgmt_navigator_failure_window configuration for the role. The value that can be specified for this threshold is the number of bytes of audits data that is left to be sent to audit server. mgmt_navigator_failure_thresholds critical:any, warning:never BYTES
Navigator Audit Pipeline Health Check Enable test of audit events processing pipeline. This will test if audit events are not getting processed by Audit Server for a role that generates audit. mgmt_navigator_status_check_enabled true no unit

Kafka Broker File Descriptors

This Kafka Broker health test checks that the number of file descriptors used does not rise above some percentage of the Kafka Broker file descriptor limit. A failure of this health test may indicate a bug in either Hadoop or Cloudera Manager. Contact Cloudera support. This test can be configured using the File Descriptor Monitoring Thresholds Kafka Broker monitoring setting.

Short Name: File Descriptors

Property Name Description Template Name Default Value Unit
File Descriptor Monitoring Thresholds The health test thresholds of the number of file descriptors used. Specified as a percentage of file descriptor limit. kafka_broker_fd_thresholds critical:70.0, warning:50.0 PERCENT

Kafka Broker Host Health

This Kafka Broker health test factors in the health of the host upon which the Kafka Broker is running. A failure of this test means that the host running the Kafka Broker is experiencing some problem. See that host's status page for more details.This test can be enabled or disabled using the Kafka Broker Host Health Test Kafka Broker monitoring setting.

Short Name: Host Health

Property Name Description Template Name Default Value Unit
Kafka Broker Host Health Test When computing the overall Kafka Broker health, consider the host's health. kafka_broker_host_health_enabled true no unit

Kafka Broker Log Directory Free Space

This Kafka Broker health test checks that the filesystem containing the log directory of this Kafka Broker has sufficient free space. This test can be configured using the Log Directory Free Space Monitoring Absolute Thresholds and Log Directory Free Space Monitoring Percentage Thresholds Kafka Broker monitoring settings.

Short Name: Log Directory Free Space

Property Name Description Template Name Default Value Unit
Log Directory Free Space Monitoring Absolute Thresholds The health test thresholds for monitoring of free space on the filesystem that contains this role's log directory. log_directory_free_space_absolute_thresholds critical:5.36870912E9, warning:1.073741824E10 BYTES
Log Directory Free Space Monitoring Percentage Thresholds The health test thresholds for monitoring of free space on the filesystem that contains this role's log directory. Specified as a percentage of the capacity on that filesystem. This setting is not used if a Log Directory Free Space Monitoring Absolute Thresholds setting is configured. log_directory_free_space_percentage_thresholds critical:never, warning:never PERCENT

Kafka Broker Process Status

This Kafka Broker health test checks that the Cloudera Manager Agent on the Kafka Broker host is heart beating correctly and that the process associated with the Kafka Broker role is in the state expected by Cloudera Manager. A failure of this health test may indicate a problem with the Kafka Broker process, a lack of connectivity to the Cloudera Manager Agent on the Kafka Broker host, or a problem with the Cloudera Manager Agent. This test can fail either because the Kafka Broker has crashed or because the Kafka Broker will not start or stop in a timely fashion. Check the Kafka Broker logs for more details. If the test fails because of problems communicating with the Cloudera Manager Agent on the Kafka Broker host, check the status of the Cloudera Manager Agent by running /etc/init.d/cloudera-scm-agent status on the Kafka Broker host, or look in the Cloudera Manager Agent logs on the Kafka Broker host for more details. This test can be enabled or disabled using the Kafka Broker Process Health Test Kafka Broker monitoring setting.

Short Name: Process Status

Property Name Description Template Name Default Value Unit
Kafka Broker Process Health Test Enables the health test that the Kafka Broker's process state is consistent with the role configuration kafka_broker_scm_health_enabled true no unit

Kafka Broker Swap Memory Usage

This Kafka Broker health test checks the amount of swap memory in use by the role. A failure of this health test may indicate that your machine is overloaded. This test can be configured using the Process Swap Memory Thresholds monitoring settings.

Short Name: Swap Memory Usage

Property Name Description Template Name Default Value Unit
Process Swap Memory Thresholds The health test thresholds on the swap memory usage of the process. process_swap_memory_thresholds critical:never, warning:any BYTES

Kafka Broker Unexpected Exits

This Kafka Broker health test checks that the Kafka Broker has not recently exited unexpectedly. The test returns "Bad" health if the number of unexpected exits exceeds a critical threshold. For example, if this test is configured with a critical threshold of 1, this test returns "Good" health if there have been no unexpected exits recently. If 1 or more unexpected exits occurred recently, this test returns "Bad" health. The test also indicates whether any of the exits were caused by an OutOfMemory error if the Cloudera Manager Kill When Out of Memory monitoring setting is enabled. This test can be configured using the Unexpected Exits Thresholds and Unexpected Exits Monitoring Period Kafka Broker monitoring settings.

Short Name: Unexpected Exits

Property Name Description Template Name Default Value Unit
Unexpected Exits Monitoring Period The period to review when computing unexpected exits. unexpected_exits_window 5 MINUTES
Unexpected Exits Thresholds The health test thresholds for unexpected exits encountered within a recent period specified by the unexpected_exits_window configuration for the role. unexpected_exits_thresholds critical:any, warning:never no unit