This topic describes the release notes for the CloudMonitor agent.
3.5.10
Item | Description |
Release date | 2023-09-08 |
New feature | moduleTask.json supports feature disabling. You no longer need to disable a feature by deleting it.
The argusagent tool top tool is provided for you to sort and show the top N -n N from the following three dimensions: -by fd (number of opened files), -by mem (memory usage), and -by cpu (CPU utilization). GPU metric data collection can be disabled. GPU metric data can be dynamically collected during the runtime of the CloudMonitor agent. The number of CPU cores can be changed dynamically during the runtime of the CloudMonitor agent. Hosts that are not provided by Alibaba Cloud but managed by Cloud Assistant are supported.
Note The CloudMonitor agent generates a minidump file when it exits unexpectedly. When the CloudMonitor agent starts next time, the minidump file is reported to CloudMonitor for analysis and bug fixing in the background, improving the stability of the CloudMonitor agent. |
Fixed issue | Data failed to be reported in a specified time zone. The number of opened files for a process ranking top five is incorrect. When a process ID is greater than 1,000,000, the precision of the reported data is degraded. After the CloudMonitor agent is installed on the Windows hosts of some existing users, argusagent cannot be started or the specified dynamic-link library (DLL) is missing. A carriage return line feed (CRLF) injection occurs when a configuration file on Windows is read. When the number of processes is collected for the first time, the collection is skipped, causing the process quantity to be 0.
|
Performance optimization | Process monitoring performance is optimized to reduce the frequency of unexpected agent exits. The installation success rate of the CloudMonitor agent on Windows is increased. When the resource usage of the CloudMonitor agent is exceeded, the top 10 resources consumed (for example, CPU utilization) are collected and the call stacks of all threads are enumerated to help analyze the resource usage.
|
3.5.8
Item | Description |
Release date | 2022-06-30 |
New feature | Files can be distributed and stored as required. The following metrics are supported: the packet loss rate, the error rate, and the number of deadlock processes. The following metrics are supported: the device usage and the swap usage.
|
Fixed issue | The size of the dir_name field is reduced to 512 bytes when it is concatenated. On Windows, GetUptime is called when a system module is called. The IphlpapiGetTcpTable function causes memory leaks. The cpu.total metric is changed from cpuPercent.combined to 1-cpu.idle. The ping probe checks whether the destination IP address used when data is sent is the same as the source IP address used when data is received. ICMP serial number collision is also fixed. On Windows, a service fails to start due to spaces contained in the argusagent path (imagePath in the registry).
|
3.5.7
Item | Description |
Release date | 2022-04-30 |
New feature | TCP metrics are supported. |
Fixed issue | Excessive data is reported when disk directories are concatenated. The CloudMonitor agent does not perform polling on the international site (alibabacloud.com). Win32 changes the .py file associations.
|
3.5.5
Item | Description |
Release date | 2021-12-30 |
New feature | Log collection is supported. |
Fixed issue | None |
3.5.4
Item | Description |
Release date | 2021-12-16 |
New feature | |
Fixed issue | The number of CPU cores collected from Container Service is inaccurate in some cases. An error occurs during IP address resolution on Windows. The CloudMonitor agent occasionally exits when the process collects the number of threads. The ping command fails to return the result of availability tests. The scheduling interval of availability tests is larger than the configured time interval in some cases.
|
3.5.3
Item | Description |
Release date | 2021-09-10 |
New feature | Exporters can be used to collect data. Requests can be redirected to HTTPS in HTTP-based availability monitoring tasks. More SSL ciphers can be used in HTTP-based availability monitoring tasks. By default, HTTP-based availability monitoring tasks have the same performance as curl commands. Headers such as user_agent are added to the requests of HTTP-based availability monitoring tasks.
|
Fixed issue | The number of TCP connections is occasionally miscalculated on IPv6 hosts. The disk usage is precise to decimal places. The CloudMonitor agent is occasionally disabled when it collects the cred metric in process monitoring tasks.
|
3.5.2
Item | Description |
Release date | 2021-06-30 |
New feature | The monitoring frequency of availability monitoring tasks can be changed. The usability of availability monitoring tasks is optimized. For example, more comprehensive and standardized local logs are recorded. The Uptime metric can be used to view the time period from the last startup time of the system to the current time.
|
Fixed issue | The CloudMonitor agent fails to be installed on some Windows hosts due to the missing of DLLs. |
3.4.10
Item | Description |
Release date | 2021-03-11 |
New feature | None |
Fixed issue | The CloudMonitor agent fails to be installed on some hosts that are not provided by Alibaba Cloud. The installation fails because the path to the AccessKey pair cannot be read. |
3.4.9
Item | Description |
Release date | 2021-01-05 |
New feature | The SOCKS5 proxy is supported. |
Fixed issue | The CloudMonitor agent fails to be installed on some hosts that are not provided by Alibaba Cloud. The installation fails due to the missing of specific DLLs. These hosts run Windows Server 2012 or earlier. |
3.4.8
Item | Description |
Release date | 2020-11-17 |
New feature | None |
Fixed issue | URLs cannot be correctly parsed by availability monitoring. |
3.4.7
Item | Description |
Release date | 2020-07-27 |
New feature | More supported metrics: The CloudMonitor agent can collect metrics about disk I/O and the utilization of a single CPU core. Less resource usage: After optimization, the CloudMonitor agent occupies fewer resources and has less impact on the system performance. System protection: When the system load is heavy or the CloudMonitor agent occupies excessive system resources due to specific reasons, the CloudMonitor agent automatically exits.
|
Fixed issue | The CloudMonitor agent for Go automatically changes the system time. |