This is an Atlas server role-level status test that checks whether the Atlas Server's login page is reachable or not. A failure of this health test indicates that the Atlas Server is not fully functional. This test can be enabled or disabled using the Atlas Server Url Canary Enabled setting.
Short Name: Atlas Server Canary
This Atlas Server health test checks that the Auditing for the Atlas Server role is getting processed correctly and is not blocked. A failure of this health test may indicate a problem with the audit pipeline of Atlas Server process. This test can fail either because the Cloudera Audit Server is not accepting audits, or the Cloudera Manager Agent on the Atlas Server 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 Atlas Server monitoring setting.
Short Name: Audit Pipeline Test
This Atlas Server health test checks that the number of file descriptors used does not rise above some percentage of the Atlas Server 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 Atlas Server monitoring setting.
Short Name: File Descriptors
This Atlas Server health test factors in the health of the host upon which the Atlas Server is running. A failure of this test means that the host running the Atlas Server is experiencing some problem. See that host's status page for more details.This test can be enabled or disabled using the Atlas Server Host Health Test Atlas Server monitoring setting.
Short Name: Host Health
This Atlas Server health test checks that the filesystem containing the log directory of this Atlas Server 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 Atlas Server monitoring settings.
Short Name: Log Directory Free Space
This Atlas Server health test checks that the Cloudera Manager Agent on the Atlas Server host is heart beating correctly and that the process associated with the Atlas Server role is in the state expected by Cloudera Manager. A failure of this health test may indicate a problem with the Atlas Server process, a lack of connectivity to the Cloudera Manager Agent on the Atlas Server host, or a problem with the Cloudera Manager Agent. This test can fail either because the Atlas Server has crashed or because the Atlas Server will not start or stop in a timely fashion. Check the Atlas Server logs for more details. If the test fails because of problems communicating with the Cloudera Manager Agent on the Atlas Server host, check the status of the Cloudera Manager Agent by running /etc/init.d/cloudera-scm-agent status on the Atlas Server host, or look in the Cloudera Manager Agent logs on the Atlas Server host for more details. This test can be enabled or disabled using the Atlas Server Process Health Test Atlas Server monitoring setting.
Short Name: Process Status
This Atlas Server 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 Atlas Server health test checks the change of the amount of swap memory usage by the role during a predefined period. A failure of this health test may indicate that your machine is overloaded. This test can be configured using the Swap Memory Usage Rate Thresholds and Swap Memory Usage Rate Window monitoring settings.
Short Name: Swap Memory Usage Rate Beta
This Atlas Server health test checks that the Atlas Server 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 Atlas Server monitoring settings.
Short Name: Unexpected Exits
