CloudMonitor:How do I troubleshoot the heartbeat check failure that is reported by the CloudMonitor agent?

The CloudMonitor agent reports an error message that indicates a failed heartbeat check if a host failure, a network exception, or the downtime of the agent occurs. In this topic, an Elastic Compute Service (ECS) instance is used as an example to describe how to troubleshoot a failed heartbeat check.

1. Check whether the ECS instance runs as expected. For more information, see View instance information.
   • If the ECS instance runs as expected, perform 2.
   • If the ECS instance does not run as expected, start or restart the ECS instance. For more information, see Start an instance or Reboot the instance.
     Note If you still receive this error message after you start o restart the ECS instance, read the related topics of ECS to check the cause. For more information, see Instance FAQ.
2. Check whether the CloudMonitor agent that is installed on the ECS instance runs as expected. For more information, see Install and uninstall the CloudMonitor agent for C++.
   • If the CloudMonitor agent runs as expected, perform 3.
   • If the CloudMonitor agent does not run as expected, restart the CloudMonitor agent. For more information, see How can I restart the CloudMonitor agent for C++?.
3. Ping the IP address that is used by CloudMonitor to receive heartbeat data on the ECS instance and check whether the network connection to the ECS instance is available.

   For more information about how to obtain the IP address that is used by CloudMonitor to receive heartbeat data, see Configure the network information.

   • If the network connection is available, perform 4.
   • If the network connection is not available, configure the network of the ECS instance. For more information, see Configure the network information.
4. Collect logs that are stored in the /usr/local/cloudmonitor/local_data/logs directory of the CloudMonitor agent and submit a ticket.