You can use the Cmonitor service to monitor your cluster.
ccm release common-services cmonctl output
Usage: cmonctl <options> [ <resource> [ <healthObject> ] ]
options:
-p : Print current state of all cmonitor resources and healthObject to the logs
-D <DEBUG> : Debug flag in decimal or hexadecimal number
-D1 <DEBUG> : Second level debug flag in decimal or hexadecimal nunmber
-lr : List all cmonitor resources and their healthObjects or healthObjects associated with a given resource
: The cmonitor service is configured with "servicemonitor" and "network" resources
-le : List all errors or errors associated with a specific resource or an healthObject associated with a resource
-ce : Clear all errors or errors associated with a specific resource or an healthObject associated with a resource
-h|--help : Print this help message and exit
Current "servicemonitor" resource healthObjects are:
ccmMonitor : Checks the health of Cluster Control Manager
bosh : Checks the health of bosh director
prometheus : Checks the health of prometheus service running in the cluster
ingress : Checks to see if external services can access services running inside the cluster via the ingress gateway
alerting : Checks the health of alerting service running in the cluster
The "network" resource healthObjects are IP address cmonitor service configured to ping periodically.
ccm release common-services updateIp output
Usage: updateIp
Cmonitor service periodically checks if CCM is reachable. It is configured with CCM IP address
during cluster deployment. This command updates the cmonitor service with new CCM IP Address
if CCM IP address has changed. If the CCM IP address has not changed, no action is taken.