CloudMonitor agent versions, requirements, and resource usage - Cloud Monitor

Agent versions

Programming language	Version	Description	References
C++ (recommended)	3.X	Latest version. Recommended.	Install and uninstall the CloudMonitor agent
Go	2.X	No longer maintained. Use the C++ agent instead.	Introduction to the CloudMonitor agent for Go Install the Cloud Monitor agent for Go
Java	1.X	No longer maintained. Use the C++ agent instead.	Introduction to the CloudMonitor agent for Java Install the CloudMonitor agent for Java

Note

The C++ agent uses less CPU and memory than the Go and Java agents, especially under heavy workloads.

Operating system	Hardware architecture
Windows 7, Windows Server 2008 R2, or later	i386 or AMD64
Linux 2.6.23 or later with the GNU C Library (commonly known as glibc)	i386, AMD64, or ARM64

Operating system

Default location

Process

Log

Linux

/usr/local/cloudmonitor

/usr/local/cloudmonitor/bin/argusagent

/usr/local/cloudmonitor/local_data/logs

Log types:

Windows

C:\Program Files\Alibaba\cloudmonitor

C:\Program Files\Alibaba\cloudmonitor\bin\argusagent

C:\Program Files\Alibaba\cloudmonitor\local_data\logs

TCP port 80, 443, 3128, or 8080: used to send heartbeats and report monitoring data to a remote server.
Port 15579: used for local configuration queries and log level changes.

Note

If your agent resource usage differs from the values below, verify that you are running the latest agent version.
Earlier versions may have memory leaks. Upgrade to the latest version.

Category	Consumption
CPU	Under normal operation, single-core CPU utilization is typically less than 3%. Note CPU utilization may spike during process startup.
Memory	Under normal operation, memory usage typically does not exceed 70 MB. Note Memory usage can reach 200 MB with multi-core CPUs, many processes, or multiple monitored devices.
Protection mechanism	If single-core CPU utilization exceeds 50% or memory exceeds 200 MB, the agent automatically exits (up to four times) to protect host resources. Note If this occurs, you can adjust your resource usage thresholds based on your business scenario. For more information, see What do I do if the process of the Cloud Monitor agent automatically exits?
Network bandwidth	Monitoring data is sent every 15 seconds (~10 KB/s on the internal network). Heartbeats are sent every 3 minutes (~2 KB/s).
Installation package	10 MB to 15 MB
Log files	10 MB per log file; up to 70 MB total
IO	Up to 1 KB/s read/write when the on-premises log monitoring feature of Hybrid Cloud Monitoring is not enabled. Note I/O usage increases with log volume when on-premises log monitoring is enabled.