Once VMware Identity Manager is clustered through, a scheduled health check is registered. This scheduled check runs every hour and might pop-up a notification on the overall postgres cluster health status. Starting from the 8.4 release, you can also view the cluster health status in the VMware Identity Manager environment card.
- VMware Identity Manager nodes reachability from vRealize Suite Lifecycle Manager.
- DelegateIP assignment to any of the cluster nodes.
- Postgres primary node existence.
- Postgres nodes having replication delay.
- Postgres nodes being marked as down in the cluster.
- Pgpool primary node existence.
- Pgpool running on all nodes.
All the above checks are captured and appropriate description messages are displayed in the notification that pops-ups with a message like vIDM postgres cluster health status is critical. For more information on the steps, see the KB article 75080.
If all the checks are validated, vRealize Suite Lifecycle Manager gives a notification with a message as vIDM postgres cluster health status is ok that provides a healthy cluster status. On a Day-2 operation, you can click the Trigger Cluster Health on the Global Environment for VMware Identity Manager in addition to scheduling the health check on an hourly basis. For more information on trigger cluster health, see Day 2 Operations for Global Environment in vRealize Suite Lifecycle Manager.
As a Day-2 operation, Pause Cluster Health Check is introduced to pause the health notifications when troubleshooting issues, such as VMware Identity Manager password management, replacing certificates, upgrade related issues, and more. When performing an hourly check or during a maintenance, you can click the Pause Cluster Health Check, and then click Submit to pause the health notifications. Once these functions are up and running, you can resume the health check in the environment product card.