To use the host monitoring feature of CloudMonitor, you must install the CloudMonitor agent on your hosts.

Important The CloudMonitor agent for Java is no longer upgraded. We recommend that you use the CloudMonitor agent for C++. For more information, see Install and uninstall the CloudMonitor agent for C++.

Installation path

  • Linux: /usr/local/cloudmonitor
  • Windows: C:\Program Files\Alibaba\cloudmonitor

Processes

After the CloudMonitor agent is installed, the following two processes run on your hosts:

  • /usr/local/cloudmonitor/jre/bin/java
  • /usr/local/cloudmonitor/wrapper/bin/wrapper

Ports

  • The CloudMonitor agent accesses and listens on TCP port 32000 of local hosts to daemonize processes.
  • The CloudMonitor agent accesses TCP port 3128, 8080, or 443 of remote hosts to send heartbeat messages and report monitoring data. The CloudMonitor agent that is installed on an Alibaba Cloud Elastic Compute Service (ECS) instance accesses port 3128 or 8080. The CloudMonitor agent that is installed on a third-party host accesses port 443.
  • The CloudMonitor agent accesses HTTP port 80 of remote hosts to obtain upgrade packages.

Logs

  • The CloudMonitor agent stores monitoring logs in the /usr/local/cloudmonitor/logs directory.
  • The CloudMonitor agent stores other logs such as logs about process startup, shutdown, and daemonization in the /usr/local/cloudmonitor/wrapper/logs directory.
  • You can modify the /usr/local/cloudmonitor/config/log4j.properties file to adjust the log level.

Resource usage

  • The /usr/local/cloudmonitor/wrapper/bin/wrapper process occupies about 1 MB of memory and few CPU resources.
  • The /usr/local/cloudmonitor/jre/bin/java process occupies about 70 MB of memory and 1% to 2% of one CPU core.
  • The size of the installation package is 70 MB. The CloudMonitor agent occupies about 200 MB of disk space after it is installed.
  • Logs can occupy up to 40 MB of disk space. When the log size exceeds 40 MB, earlier logs are deleted.
  • The CloudMonitor agent reports monitoring data at an interval of 15 seconds, which occupies about 10 KB/s of network bandwidth.
  • The CloudMonitor agent sends heartbeat messages at an interval of 3 minutes, which occupies about 2 KB/s of network bandwidth.

External dependencies

  • The CloudMonitor agent is built in with Java Runtime Environment (JRE) 1.8.
  • Java Service Wrapper is used to provide features such as daemonizing processes, starting processes at the system boot, and registering the CloudMonitor agent as a Windows service.
  • The CloudMonitor agent runs the ss -s command to collect the number of TCP connections. If your operating system does not support this command, you must install the iproute utility.

Installation guide

For more information, see Install the CloudMonitor agent for Java.

Install the CloudMonitor agent on a third-party host

  1. Log on to the CloudMonitor console.
  2. In the left-side navigation pane, click Host Monitoring.
  3. On the Host Monitoring page, click Install on Third-party Host. In the Install CloudMonitor Agent panel, select the type and operating system of the host and install the CloudMonitor agent as instructed.