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

Short Name: Audit Pipeline Test

This is a Telemetry Publisher health test that checks whether data is exported succesfully for stream HIVE-query-audits. A failure of this check indicates that one or more exports failed.

Short Name: Data Export Test For Stream Hive-Query-Audits

This is a Telemetry Publisher health test that checks whether data is exported succesfully for stream IMPALA-query-profile. A failure of this check indicates that one or more exports failed.

Short Name: Data Export Test For Stream Impala-Query-Profile

This is a Telemetry Publisher health test that checks whether data is exported succesfully for stream OOZIE-workflows. A failure of this check indicates that one or more exports failed.

Short Name: Data Export Test For Stream Oozie-Workflows

This is a Telemetry Publisher health test that checks whether data is exported succesfully for stream SPARK2_ON_YARN-event-log. A failure of this check indicates that one or more exports failed.

Short Name: Data Export Test For Stream Spark2_on_yarn-Event-Log

This is a Telemetry Publisher health test that checks whether data is exported succesfully for stream YARN-apps. A failure of this check indicates that one or more exports failed.

Short Name: Data Export Test For Stream Yarn-Apps

This is a Telemetry Publisher health test that checks whether data is exported succesfully for stream YARN-jhist. A failure of this check indicates that one or more exports failed.

Short Name: Data Export Test For Stream Yarn-Jhist

This is a Telemetry Publisher health test that checks whether data is ingested succesfully by stream HIVE-query-audits. A failure of this check indicates that one or more ingests failed.

Short Name: Data Ingest Test For Stream Hive-Query-Audits

This is a Telemetry Publisher health test that checks whether data is ingested succesfully by stream IMPALA-query-profile. A failure of this check indicates that one or more ingests failed.

Short Name: Data Ingest Test For Stream Impala-Query-Profile

This is a Telemetry Publisher health test that checks whether data is ingested succesfully by stream OOZIE-workflows. A failure of this check indicates that one or more ingests failed.

Short Name: Data Ingest Test For Stream Oozie-Workflows

This is a Telemetry Publisher health test that checks whether data is ingested succesfully by stream SPARK2_ON_YARN-event-log. A failure of this check indicates that one or more ingests failed.

Short Name: Data Ingest Test For Stream Spark2_on_yarn-Event-Log

This is a Telemetry Publisher health test that checks whether data is ingested succesfully by stream YARN-apps. A failure of this check indicates that one or more ingests failed.

Short Name: Data Ingest Test For Stream Yarn-Apps

This is a Telemetry Publisher health test that checks whether data is ingested succesfully by stream YARN-jhist. A failure of this check indicates that one or more ingests failed.

Short Name: Data Ingest Test For Stream Yarn-Jhist

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

Short Name: File Descriptors

This Telemetry Publisher health test checks that the Telemetry Publisher is not spending too much time performing Java garbage collection. It checks that no more than some percentage of recent time is spent performing Java garbage collection. A failure of this health test may indicate a capacity planning problem or misconfiguration of the Telemetry Publisher. This test can be configured using the Garbage Collection Duration Thresholds and Garbage Collection Duration Monitoring Period Telemetry Publisher monitoring settings.

Short Name: GC Duration

This Telemetry Publisher health test checks that the filesystem containing the heap dump directory of this Telemetry Publisher 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 Telemetry Publisher monitoring settings.

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

This Telemetry Publisher 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 is a Telemetry Publisher health test that checks that the filesystem containing the Telemetry Publisher Data Directory of this Telemetry Publisher has sufficient free space. See the Telemetry Publisher Data Directory description on the Telemetry Publisher configuration page for more information on this directory type. This test can be configured using the Telemetry Publisher Data Directory Free Space Monitoring Absolute Thresholds and Telemetry Publisher Data Directory Free Space Monitoring Percentage Thresholds Telemetry Publisher monitoring settings.

Short Name: Telemetry Publisher Data Directory Free Space

This Telemetry Publisher health test checks that the Telemetry Publisher 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 Telemetry Publisher monitoring settings.

Short Name: Unexpected Exits

This health test checks that the role's web server is responding quickly to requests by the Cloudera Manager Agent, and that the Cloudera Manager Agent can collect metrics from the web server. Failure of this health test may indicate a problem with the web server of the Telemetry Publisher, a misconfiguration of the Telemetry Publisher, or a problem with the Cloudera Manager Agent. Consult the Cloudera Manager Agent logs and the logs of the Telemetry Publisher for more detail. If the test failure message indicates a communication problem, the Cloudera Manager Agent's HTTP requests to the Telemetry Publisher's web server are failing or timing out. If the test's failure message indicates an unexpected response, the Telemetry Publisher's web server responded to the Cloudera Manager Agent's request, but the response could not be interpreted for some reason. This test can be configured using the Web Metric Collection Telemetry Publisher monitoring setting.

Short Name: Web Server Status