This Reports Manager health test checks that the Auditing for the Reports Manager role is getting processed correctly and is not blocked. A failure of this health test may indicate a problem with the audit pipeline of Reports Manager process. This test can fail either because the Cloudera Audit Server is not accepting audits, or the Cloudera Manager Agent on the Reports Manager 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 Reports Manager monitoring setting.

Short Name: Audit Pipeline Test

This is a Reports Manager health test that checks if the Cloudera Manager descriptor has been refreshed recently. The Cloudera Manager descriptor is used to pass configuration information from the Cloudera Manager Server to the Reports Manager. If the descriptor becomes stale, Reports Manager operation may be impacted because the Reports Manager will receive information about new hosts, roles, and services, or changes to existing hosts, roles, and services. A stale descriptor usually indicates problems communicating with the Cloudera Manager Server but can also indicate performance problems or a bug. Consult the Reports Manager log and the Cloudera Manager Server log for more information. This test can be configured using the Cloudera Manager Descriptor Age Thresholds Cloudera Manager Reports Manager setting.

Short Name: Cloudera Manager Descriptor Age

This Reports Manager health test checks that the number of file descriptors used does not rise above some percentage of the Reports Manager 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 Reports Manager monitoring setting.

Short Name: File Descriptors

This Reports Manager health test checks that the filesystem containing the heap dump directory of this Reports Manager has sufficient free space. This test can be configured using the Heap Dump Directory Free Space Monitoring Absolute Thresholds and Heap Dump Directory Free Space Monitoring Percentage Thresholds Reports Manager monitoring settings.

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

This Reports Manager health test checks that the filesystem containing the log directory of this Reports Manager 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 Reports Manager monitoring settings.

Short Name: Log Directory Free Space

This Reports Manager health test checks that the Reports Manager threads are not experiencing long scheduling pauses. The test uses a pause monitoring thread in the Reports Manager that tracks scheduling delay by noting if it is run on its requested schedule. If the thread is not run on its requested schedule, the delay is noted and considered pause time. The health test checks that no more than some percentage of recent time is spent paused. A failure of this health test may indicate that the Reports Manager is not getting enough CPU resources, or that it is spending too much time doing garbage collection. Inspect the Reports Manager logs for any pause monitor output and check garbage collection metrics exposed by the Reports Manager. This test can be configured using the Pause Duration Thresholds and Pause Duration Monitoring Period Reports Manager monitoring settings.

Short Name: Pause Duration

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

Short Name: Process Status

This is a Reports Manager health test that checks that the filesystem containing the Reports Manager Working Directory of this Reports Manager has sufficient free space. See the Reports Manager Working Directory description on the Reports Manager configuration page for more information on this directory type. This test can be configured using the Reports Manager Working Directory Free Space Monitoring Absolute Thresholds and Reports Manager Working Directory Free Space Monitoring Percentage Thresholds Reports Manager monitoring settings.

Short Name: Reports Manager Working Directory Free Space

This Reports Manager 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

This Reports Manager health test checks that the Reports Manager 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 occured 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 Reports Manager monitoring settings.

Short Name: Unexpected Exits