About the Health Check Page

To access the Health Checks page, click Settings > Health Checks on the banner.

The Deployment Shell request deployment health-check command retrieves and displays the status of the Routing Director cluster health on the CLI. In addition to the command, a periodic cron job runs hourly, by default, similarly checking the health status of the cluster. The results of the health check, whether executed manually or through the cron job, are stored in a health-check database.

Click Settings > Health Checks to view the result and output of the most recent health-check command on the Routing Director GUI. With this feature, you can check cluster health from the GUI without having to log in to a node VM.

The output matches the command output on the CLI. The latest health-check output is retrieved from the health-check database is displayed irrespective of whether the cluster health was checked manually or through the cron job. Additionally, if a health-check command is in progress at the time you access this page, the output on the page reflects the output on the CLI at the particular moment you access the page. To refresh the page, click Settings > Health Checks again, and view the updated output.

Note: Clicking Health Checks does not initiate a health-check but only displays the output of the most recent cluster status check.

Table 1 describes the fields displayed on the Heath Checks page.

Table 1: Fields on the Health Checks page
Field	Description
Overall Cluster Status	Describes the final output of the latest cluster health check. The status can be GREEN, AMBER, or RED. A green status indicates a healthy cluster, and a red status indicates serious issues in the cluster. An amber status indicates that there maybe certain noncritical issues in the cluster.
Status Details	Expand this section to view the detailed and complete output of the health check. The health-check command checks for multiple parameters such as the status of the node (readiness, diskpressure, pod-status, CPU and memory usage, taints-status, and I/O latency), status of databases and services, and so on. The output matches the command output on the CLI.
Last Checked	Displays the date and time stamp of the latest check command output displayed in the yyyy-mm-dd hh:mm:ss format.