Navigator Thales KMS Metastore Health Tests
Navigator Thales KMS Metastore Audit Pipeline Test
This Navigator Thales KMS Metastore health test checks that the Auditing for the Navigator Thales KMS Metastore role is getting processed correctly and is not blocked. A failure of this health test may indicate a problem with the audit pipeline of Navigator Thales KMS Metastore process. This test can fail either because the Cloudera Audit Server is not accepting audits, or the Cloudera Manager Agent on the Navigator Thales KMS Metastore 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 Navigator Thales KMS Metastore monitoring setting.
Short Name: Audit Pipeline Test
Monitoring Period For Audit Failures
- Description
- The period to review when checking if audits are blocked and not getting processed.
- Template Name
- mgmt_navigator_failure_window
- Default Value
- 20
- Unit(s)
- MINUTES
Navigator Audit Failure Thresholds
- Description
- 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.
- Template Name
- mgmt_navigator_failure_thresholds
- Default Value
- critical:any, warning:never
- Unit(s)
- BYTES
Navigator Audit Pipeline Health Check
- Description
- 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.
- Template Name
- mgmt_navigator_status_check_enabled
- Default Value
- true
- Unit(s)
- no unit
Navigator Thales KMS Metastore File Descriptors
This Navigator Thales KMS Metastore health test checks that the number of file descriptors used does not rise above some percentage of the Navigator Thales KMS Metastore 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 Navigator Thales KMS Metastore monitoring setting.
Short Name: File Descriptors
File Descriptor Monitoring Thresholds
- Description
- The health test thresholds of the number of file descriptors used. Specified as a percentage of file descriptor limit.
- Template Name
- hsmkp_metastore_thales_fd_thresholds
- Default Value
- critical:70.0, warning:50.0
- Unit(s)
- PERCENT
Navigator Thales KMS Metastore Host Health
This Navigator Thales KMS Metastore health test factors in the health of the host upon which the Navigator Thales KMS Metastore is running. A failure of this test means that the host running the Navigator Thales KMS Metastore is experiencing some problem. See that host's status page for more details.This test can be enabled or disabled using the Navigator Thales KMS Metastore Host Health Test Navigator Thales KMS Metastore monitoring setting.
Short Name: Host Health
Navigator Thales KMS Metastore Host Health Test
- Description
- When computing the overall Navigator Thales KMS Metastore health, consider the host's health.
- Template Name
- hsmkp_metastore_thales_host_health_enabled
- Default Value
- true
- Unit(s)
- no unit
Navigator Thales KMS Metastore Process Status
This Navigator Thales KMS Metastore health test checks that the Cloudera Manager Agent on the Navigator Thales KMS Metastore host is heart beating correctly and that the process associated with the Navigator Thales KMS Metastore role is in the state expected by Cloudera Manager. A failure of this health test may indicate a problem with the Navigator Thales KMS Metastore process, a lack of connectivity to the Cloudera Manager Agent on the Navigator Thales KMS Metastore host, or a problem with the Cloudera Manager Agent. This test can fail either because the Navigator Thales KMS Metastore has crashed or because the Navigator Thales KMS Metastore will not start or stop in a timely fashion. Check the Navigator Thales KMS Metastore logs for more details. If the test fails because of problems communicating with the Cloudera Manager Agent on the Navigator Thales KMS Metastore host, check the status of the Cloudera Manager Agent by running /etc/init.d/cloudera-scm-agent status on the Navigator Thales KMS Metastore host, or look in the Cloudera Manager Agent logs on the Navigator Thales KMS Metastore host for more details. This test can be enabled or disabled using the Navigator Thales KMS Metastore Process Health Test Navigator Thales KMS Metastore monitoring setting.
Short Name: Process Status
Navigator Thales KMS Metastore Process Health Test
- Description
- Enables the health test that the Navigator Thales KMS Metastore's process state is consistent with the role configuration
- Template Name
- hsmkp_metastore_thales_scm_health_enabled
- Default Value
- true
- Unit(s)
- no unit
Navigator Thales KMS Metastore Swap Memory Usage
This Navigator Thales KMS Metastore 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
Process Swap Memory Thresholds
- Description
- The health test thresholds on the swap memory usage of the process. This takes precedence over the host level threshold.
- Template Name
- process_swap_memory_thresholds
- Default Value
- critical:never, warning:200.0
- Unit(s)
- BYTES
Navigator Thales KMS Metastore Unexpected Exits
This Navigator Thales KMS Metastore health test checks that the Navigator Thales KMS Metastore 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 Navigator Thales KMS Metastore monitoring settings.
Short Name: Unexpected Exits
Unexpected Exits Monitoring Period
- Description
- The period to review when computing unexpected exits.
- Template Name
- unexpected_exits_window
- Default Value
- 5
- Unit(s)
- MINUTES
Unexpected Exits Thresholds
- Description
- The health test thresholds for unexpected exits encountered within a recent period specified by the unexpected_exits_window configuration for the role.
- Template Name
- unexpected_exits_thresholds
- Default Value
- critical:any, warning:never
- Unit(s)
- no unit
