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

Short Name: File Descriptors

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

This Agent health test checks that the Agent has not recently exited unexpectedly. The test returns "Bad" health if the number of unexpected exits goes above a critical threshold. For example, if this test is configured with a critical threshold of 1, this test would return "Good" health if there have been no unexpected exits recently. If there has been 1 or more unexpected exits recently, this test would return "Bad" health. This test can be configured using the Unexpected Exits Thresholds and Unexpected Exits Monitoring Period Agent monitoring settings.

Short Name: Unexpected Exits

This Agent health test checks that the web server of the Agent is responding quickly to requests by the Cloudera Manager Agent, and that the Cloudera Manager Agent can collect metrics from the web server. A failure of this health test may indicate a problem with the web server of the Agent, a misconfiguration of the Agent or a problem with the Cloudera Manager Agent. Consult the Cloudera Manager Agent logs and the logs of the Agent for more detail. If the test's failure message indicates a communication problem, this means that the Cloudera Manager Agent's HTTP requests to the Agent's web server are failing or timing out. These requests are completely local to the Agent's host, and so should never fail under normal conditions. If the test's failure message indicates an unexpected response, then the Agent's web server responded to the Cloudera Manager Agent's request, but the Cloudera Manager Agent could not interpret the response for some reason. This test can be configured using the Web Metric Collection Agent monitoring setting.

Short Name: Web Server Status