A CloudMonitor agent is registered as stopped if the agent does not respond to a heartbeat for five times consecutively (or for 15 minutes, with each internal of its heartbeat mechanism lasting three minutes). The agent may have stopped due to one of the following reasons:

  1. The agent fails to communicate with the CloudMonitor instance.
  2. The CloudMonitor process has ended.

The agent fails to communicate with the CloudMonitor instance

If the agent ran normally before the exception occurred, you can reinstall it. To do so, follow these steps:

  1. Log on to the CloudMonitor Console.
  2. In the left-side navigation pane, select Host Monitoring.
  3. Select the target host and click Install, or install the agent manually. For more information, see Install CloudMonitor GoLang agent.

The CloudMonitor process has ended

You can check CloudMonitor logs to verify whether the CloudMonitor process has ended, which is a problem that may be due to a bug. If you suspect a bug is the cause, we recommend that you open a ticket for consultation, but you should do so only after verifying that the CloudMonitor process has ended. Do so by following these steps:

  1. Check CloudMonitor logs.
    • Linux: /usr/local/cloudmonitor/logs
    • Windows: C:/Program Files/Alibaba/cloudmonitor/logs
  2. Check the agent running status.
    • Linux:
      sudo /usr/local/cloudmonitor/wrapper/bin/cloudmonitor.sh status
    • Windows:
      C:\"Program Files (x86)"\Alibaba\cloudmonitor\wrapper\bin\AppCommand.bat status

    In Linux, you can run the command /usr/local/cloudmonitor/wrapper/bin/cloudmonitor.sh to view more details.