This topic describes the release notes of the Cloud Monitor agent for host monitoring.

V2.1.55

Release date: January 24, 2019

Feature optimization and bug fixes:

Fixed the bug that prevented the agent from collecting monitoring data after an Elastic Compute Service (ECS) instance restarts.

Update recommendations:

If your host runs a GoLang agent of an earlier version, we recommend that you update the agent to V2.1.55.

V2.1.54

Release date: January 3, 2019

Feature optimization and bug fixes:

Fixed the bug that prevented the agent from collecting monitoring data from a GPU-accelerated instance that runs a Windows operating system.

Update recommendations:

If your host is a GPU-accelerated instance that runs a GoLang agent of an earlier version in a Windows operating system, we recommend that you update the agent to V2.1.54.

V2.1.53

Release date: December 25, 2018

Feature optimization and bug fixes:

Fixed the bug that prevented the agent from collecting monitoring data from an ECS instance that runs on the classic network.

Update recommendations:

If your host runs a GoLang agent of an earlier version on the classic network, we recommend that you update the agent to V2.1.53.

V2.1.51

Release date: December 4, 2018

Feature optimization and bug fixes:

  • Fixed the bug that displayed the mount point for disk monitoring as a hexadecimal string.
  • Added the pre-checks for the operating system version, system memory size, free disk space, and connectivity to the Cloud Monitor server before the installation to determine whether the agent can be installed.

Update recommendations:

If your host runs a GoLang agent of an earlier version, we recommend that you update the agent to V2.1.51.

V2.1.50

Release date: November 29, 2018

New features:

Released the Cloud Monitor GoLang agent. Compared with the Java agent, the GoLang agent reduces the resource consumption and provides more stable monitoring services. For more information, see CloudMonitor GoLang agent overview.

Update recommendations:

If your host runs a Java agent of V1.X.X, we recommend that you update the agent to V2.1.50. To update the agent, select hosts from the instance list on the Host Monitoring page and click Batch Install.

V1.2.11

New features:

Added the feature of local and remote detection by using Telnet or HTTP.

Feature optimization and bug fixes:

  • Fixed the bug that may cause the privilege escalation vulnerability when the tmp directory is used as the temporary download directory of the installation script.
  • Fixed the bug that submitted identical device data when the same disk is attached more than once.
  • Fixed the bug that prevented specific processes from obtaining the path and name.
  • Optimized the file download method to prevent the download process from blocking the monitoring process.

Update recommendations

If you need to use the feature of local health check, update the agent to V1.2.11.

V1.1.64

Feature optimization and bug fixes:

Adjusted the collection logic for memory usage. In CentOS later than 7.2, the Cloud Monitor agent obtains the available memory size from the /proc/meminfo MemAvailable field. The use of this field improves the accuracy of memory usage calculation.

Update recommendations:

If your host runs CentOS later than 7.2, we recommend that you update the agent to V1.1.64.

V1.1.63

Feature optimization and bug fixes:

  • Changed the default level of wrapper logs to info.
  • Added log information of the error level for easy failure location.
  • Fixed the bug that may cause memory leakage for logs at the debug level.

V1.1.62

Feature optimization and bug fixes:

  • Optimized the selection logic of the HTTP proxy to improve the success rate of installing the agent.
  • Added key logs for easy failure location.

V1.1.61

Feature optimization and bug fixes:

Fixed the bug that may cause exceptions when the agent collects process usernames in specific systems. When the exceptions occur, the collected top N processes are inaccurate.

V1.1.59

Feature optimization and bug fixes:

  • Optimized the method to count processes. The optimized method improves the monitoring performance.
  • Adjusted process monitoring so that two processes of the Cloud Monitor agent are excluded from the process count collection.