Help Center/ Cloud Eye/ User Guide/ Cloud Resource Monitoring/ Server Monitoring/ Cloud Eye Plug-in (Agent)/ Installing the Agent

Updated on 2026-06-18 GMT+08:00

Installing the Agent

The Agent can collect metric data from the target server OS and send it to Cloud Eye for analysis. You can view such data in graphs to monitor metrics in real time. You can also set alarm rules for key metrics to quickly identify faults.

After the Agent is installed, Cloud Eye can provide proactive and fine-grained OS monitoring for servers. The Agent can be automatically installed on mainstream OSs. You can click Install & Upgrade the Agent on the Server Monitoring page to install the Agent. You can also select Detailed monitoring to install the Agent when you buy an ECS. All OSs that support one-click installation support automatic Agent installation.

This section describes how to install the Agent automatically across all servers or selected servers, as well as how to manually install it on a single server or in batches.

Applicable scenarios

**Table 1** Applicable scenarios
Installation Method	Scenario	Constraints	Navigation Path
Automatically Installing Agents on All Servers	Cloud Eye supports one-click Agent installation on the console. If you want to install the Agent for all servers in the server monitoring list, you are advised to choose this installation method. After the installation is complete, you can manually install the Agent for servers that do not support one-click installation or those failed automatic installation.	Mainstream OSs support one-click installation. For details about supported OSs, see What OSs Does the Agent Support?	Go to the Server Monitoring page of the Cloud Eye console. Choose Install & Upgrade the Agent > Install and Upgrade Agent on All Servers above the server list.
Customizing the Automatic Agent Installation	Cloud Eye supports one-click Agent installation for servers on the console. If you only need to install the Agent for some servers that support one-click installation, you can use Cloud Eye to automate the process.		Go to the Server Monitoring page of the Cloud Eye console. Choose Install & Upgrade the Agent > Batch Install and Upgrade Agent above the server list.
Installing the Agent on a Single Server	If a server does not support or failed one-click Agent installation, you can manually install the Agent for it. For details about supported OSs, see What OSs Does the Agent Support?	None	Log in to a server.
Manually Installing the Agents in Batches	If you have multiple Linux servers in the same VPC and they do not support one-click installation, you can install the Agent for them in batches. Remote batch installation: Enter the IP address, port number, and root password or key of the servers on the console, and then run the installation commands. Local batch installation: Log in to a server and run the installation command to install the Agents for servers in batches.	Only Linux servers are supported. The servers for batch Agent installation must be deployed in the same VPC.	Remote batch installation: Go to the Server Monitoring page of the Cloud Eye console and click Install Remotely above the list. Local batch installation: Log in to a server.

Automatically Installing Agents on All Servers

Prerequisites

Required permissions have been granted to the Agent in the current region. For details, see Granting Agent Permissions for Servers by Clicking Configure.
Before installing the Agent, ensure that the DNS server addresses and security group rules are properly configured. For details, see How Do I Configure DNS and Security Groups?

Procedure

Log in to the Cloud Eye console.
In the navigation pane, choose Server Monitoring > Elastic Cloud Server.
Choose Install & Upgrade the Agent > Install and Upgrade Agent on All Servers. The Agent installation and upgrade guidelines will be displayed on the right pane.
Figure 1 Installing and upgrading the Agent on all servers
Install the Agent as instructed.
1. Select an installation method.
  - Install or upgrade the Agent to the latest version on all ECSs: Install the Agent for all ECSs that support one-click installation but without the Agent installed, and upgrade the Agent for all ECSs with the Agent installed.
  - Install the Agent: Install the Agent on all ECSs that support one-click installation but without the Agent installed.
  - Upgrade the Agent: Upgrade the Agent for all ECSs with the Agent installed.
2. Select an Agent edition.
  - Basic edition provides basic OS monitoring metrics, including CPU, memory, file system, disk, NIC, and network metrics.
  - Enhanced edition provides GPU and BMS hardware monitoring, in addition to the capabilities provided in the basic edition.
  Install the Agent of the enhanced edition if you indeed need it because it collects more metrics, which may occupy more server resources.
Click OK.
Check the Agent installation results.
1. In the navigation pane, choose Task Center.
2. In the right pane, click the Agent Maintenance tab to view the task status.
  - If Status is Successful, the Agent is installed. On the Server Monitoring page, check that the Agent status is Running and the Agent version is the latest.
  - If Status is Timeout, click Retry in the Operation column.

Customizing the Automatic Agent Installation

Prerequisites

Required permissions have been granted to the Agent in the current region. For details, see Granting Agent Permissions for Servers by Clicking Configure.
Before installing the Agent, ensure that the DNS server addresses and security group rules are properly configured. For details, see How Do I Configure DNS and Security Groups?

Procedure

Log in to the Cloud Eye console.
In the navigation pane, choose Server Monitoring > Elastic Cloud Server.
Select the target servers and choose Install & Upgrade the Agent > Batch Install and Upgrade Agent. The Agent installation and upgrade guide will be displayed on the right.
Figure 2 Batch installing and upgrading the Agent
On the Batch Modify Servers page, check the servers with ongoing tasks. If any inoperable servers are identified, rectify the fault by referring to Why Can't I Install or Upgrade Agents in Batch?
Click Next. The Install & Upgrade the Agent page is displayed.
1. Select an installation method.
  - Install or upgrade the Agent to the latest version on all ECSs: Install the Agent for all ECSs that support one-click installation but without the Agent installed, and upgrade the Agent for all ECSs with the Agent installed.
  - Install the Agent: Install the Agent on all ECSs that support one-click installation but without the Agent installed.
  - Upgrade the Agent: Upgrade the Agent for all ECSs with the Agent installed.
2. Select an Agent edition.
  - Basic edition provides basic OS monitoring metrics, including CPU, memory, file system, disk, NIC, and network metrics.
  - Enhanced edition provides GPU and BMS hardware monitoring, in addition to the capabilities provided in the basic edition.
  Install the Agent of the enhanced edition if you indeed need it because it collects more metrics, which may occupy more server resources.
Click OK.
Check the Agent installation results.
1. In the navigation pane, choose Task Center.
2. In the right pane, click the Agent Maintenance tab to view the task status.
  - If Status is Successful, the Agent is installed. On the Server Monitoring page, check that the Agent status is Running and the Agent version is the latest.
  - If Status is Timeout, click Retry in the Operation column.

Installing the Agent on a Single Server

Prerequisites

Required permissions have been granted to the Agent in the current region. For details, see Granting Agent Permissions for Servers by Clicking Configure.
Before installing the Agent, ensure that the DNS server addresses and security group rules are properly configured. For details, see How Do I Configure DNS and Security Groups?

Ensure that you have the read and write permissions for the installation directory and the Telescope process is not stopped by other software after the installation (user root for Linux servers and user Administrator for Windows servers).

You can only use the administrator account to install the Cloud Eye Agent. Any improper use of this account may cause system stability or data security issues. Exercise caution when using this account.

Log in to the Cloud Eye console.
In the navigation pane, choose Server Monitoring > Elastic Cloud Server.
Click Install Manually above the server list. The installation guide is displayed on the right.
Figure 3 Agent installation guide
Obtain the installation command.
1. Select Linux.
2. Select Normal installation.
3. Click next to the installation command to copy the command.
Log in to the server as user root. For details, see Logging In to a Linux ECS.
Run the installation command obtained in 4.
Check whether Telescope process starts successfully. is displayed. If yes, the installation is successful. Wait for 3 to 5 minutes until the Agent starts collecting monitoring data.

Figure 4 Successful installation

Log in to the Cloud Eye console.
In the navigation pane, choose Server Monitoring > Elastic Cloud Server.
Click Install Manually above the server list. The installation guide is displayed on the right.
Figure 5 Agent installation guide
Obtain the link for downloading the installation package.
1. Select Windows.
2. Click next to the download command to copy the address for downloading the Agent installation package.
Log in to the server as an administrator. For details, see Logging In to a Windows ECS.
Enter the download address obtained in 4 in the address box to download the package.
Open Windows PowerShell and run the following command to install the Agent:
```
cd C:\Users\Administrator\Downloads; 
.\install_amd64.exe -u 0.2.3 -t 2.7.6
```
Figure 6 Installing the Agent
Check the Agent installation results.
If the Agent status is Running, the Agent is installed and started.

Manually Installing the Agents in Batches

If multiple Linux servers are deployed in the same VPC and they do not support one-click installation, you can install the Agents for these servers in batches.

Constraints

Batch installation cannot be performed across regions.
The servers where the Agent is to be installed in a batch must be in the same VPC.

Agents cannot be installed on Windows servers in batches.

Prerequisites

Required permissions have been granted to the Agent in the current region. For details, see Granting Agent Permissions for Servers by Clicking Configure.
Before installing the Agent, ensure that the DNS server addresses and security group rules are properly configured. For details, see How Do I Configure DNS and Security Groups?

There is one server with the Agent installed in the given VPC.
You have obtained the login password or key of the root user for all servers.

To batch install the Agent, you can enter the IP address, port No., and root password or key of the servers on the management console, and then run the installation command.

Log in to the Cloud Eye console.
In the navigation pane, choose Server Monitoring > Elastic Cloud Server.

Click Install Remotely to check the remote installation guide.

Install the Agent as instructed.

Select an Agent edition.
- Basic edition provides basic OS monitoring metrics, including CPU, memory, file system, disk, NIC, and network metrics.
- Enhanced edition provides GPU and BMS hardware monitoring, in addition to the capabilities provided in the basic edition.
Select an installation server.
- In the given VPC, select the server with the Agent installed as the installation server. Then use this server to install Agents on other servers in the same VPC. If there is no such an installation server, you can locate a server and choose More > Set Installation Server in the Operation column.
- If none of the servers in the VPC has the Agent installed, select one to manually install the Agent. For details, see Installing the Agent on a Single Server.
Set parameters for the servers requiring the Agent based on Table 2.

Figure 7 Remote installation
Click to enlarge

**Table 2** Parameters for configuring servers
Parameter	Description	Example Value
Server IP Address	IP address of the server for remotely installing the Agent.	192.168.72.229
Login Username	Account for logging in to the server. The default value is root and cannot be changed.	root
Login Port	Port number for remotely logging in to the server. The default value is 22. To change the remote login port, see How Can I Change a Remote Login Port?	22
Authentication	Authentication mode for logging in to the server. You can select Password or SSH key.	SSH key
Password/SSH Key	Enter the password or SSH key for logging in to the server.	Example key: -----BEGIN RSA PRIVATE KEY----- ****** -----END RSA PRIVATE KEY-----
Operation	Operations on server configurations. You can delete or copy the information.	Copy

After the configuration is complete, click OK.
Check the Agent installation results.
1. In the navigation pane, choose Task Center.
2. In the right pane, click the Agent Maintenance tab to view the task status.
  - If Status is Successful, the Agent is installed. On the Server Monitoring page, check that the Agent status is Running and the Agent version is the latest.
  - If Status is Timeout, click Retry in the Operation column.

In the given VPC, you can log in to the server with the Agent installed and run the batch installation command to install the Agent.

Currently, some regions support parsing commas (,) in passwords. This feature will be available in other regions later. If this feature is not available in your region, use a password that does not contain commas (,) when selecting the installation command.

Log in to the Cloud Eye console.
In the navigation pane, choose Server Monitoring > Elastic Cloud Server.
Click Install Manually above the server list. The installation guide is displayed on the right.
Obtain the installation command.
1. Select Linux.
2. Select Batch Installation.
3. Click next to the installation command to copy the command.
  Figure 8 Obtaining the batch Agent installation command
Log in to the ECS with the Agent installed as user root.
For details, see Login Overview (Linux).
After the login is successful, upload prepared files based on the login mode.
- Username and password: As you have collected IP addresses of all ECSs and the password of user root, keep them in the iplist.txt file and upload them to the /usr/local directory on the first ECS.
  - Passwords without commas (,) appear on separate lines in the iplist.txt file, formatted as IP address,Password of user root.
    In the following example, abcd is the password.
    
    192.168.1.1,abcd 192.168.1.2,abcd
  - Passwords with commas (,) appear on separate lines in the iplist.txt file, formatted as IP address Password of user root.
    In the following example, ab,cd is the password.
    
    192.168.1.1 ab,cd 192.168.1.2 ab,cd
- Key: As you have collected IP addresses of all ECSs, keep them in the iplist.txt file, upload them to the /usr/local directory on the first ECS, and upload the key file user.pem to the /usr/local directory on the ECS.
  In the iplist.txt file, each line contains only one IP address.
  
  Example:
```
192.168.1.1
192.168.1.2
```
Run the command obtained in 4 to install the Agents in batches.
- If you use the account and password for login and the password does not contain commas (,), or if you use the key for login, run the command directly.
- If you use the account and password for login and the password contains commas (,), add the -s true parameter to the obtained installation command.
  Take the CN North-Beijing4 region as an example. The installation command is as follows:
```
cd /usr/local && curl -k -O https://uniagent-cn-north-4.obs.cn-north-4.myhuaweicloud.com/package/batch_agent_install.sh && bash batch_agent_install.sh -r cn-north-4 -u 0.2.3 -t 2.8.2 -s true
```
Check the Agent installation results.
If the message "install successfully." is displayed, the installation is successful. Wait for 3 to 5 minutes until the Agent starts collecting monitoring data.

OSs Supported by the Agent

When purchasing an ECS running any of the OSs that support one-click Agent installation, you can select Enable Detailed Monitoring to automatically install the Agent.

The Agent-supported OSs in the following table consist of two parts:

Some OSs are built based on public images provided by Huawei Cloud IMS. For details about the IMS public image change history, see Image Update History (x86) or Image Update History (Arm). The supported images are subject to those displayed on the console.
Some OSs are built based on non-public images that have been verified by Cloud Eye to support Agent installation.

OS	Version	Agent Installation (ECS)	One-Click Agent Installation (ECS)	Agent Installation (BMS)
Windows NOTE: One-click installation on Windows is available only in some regions. This feature will be available in other regions later. For details, check the console.	Windows 2012	Supported	Not supported	Supported
	Windows 2016	Supported	Supported	Supported
	Windows 2019	Supported	Supported	Supported
	Windows 2022	Supported	Supported	Supported
CentOS	CentOS 6.9 64-bit	Supported	Not supported	Not supported
	CentOS 6.10 64-bit	Supported	Not supported	Not supported
	CentOS 7.2 64-bit	Supported	Supported	Supported
	CentOS 7.3 64-bit	Supported	Supported	Supported
	CentOS 7.4 64-bit	Supported	Supported	Supported
	CentOS 7.5 64-bit	Supported	Supported	Not supported
	CentOS 7.6 64-bit	Supported	Supported	Supported
	CentOS 7.6 64-bit (Arm)	Not supported	Not supported	Supported
	CentOS 7.7 64-bit	Supported	Supported	Not supported
	CentOS 7.8 64-bit	Supported	Supported	Not supported
	CentOS 7.9 64-bit	Supported	Supported	Supported
	CentOS 8.0 64-bit	Supported	Supported	Not supported
	CentOS 8.1 64-bit	Supported	Supported	Not supported
	CentOS 8.2 64-bit	Supported	Supported	Not supported
	CentOS Stream 8/x86	Supported	Not supported	Not supported
	CentOS Stream 8/Arm	Supported	Not supported	Not supported
	CentOS Stream 9/x86	Supported	Not supported	Not supported
Alma Linux	AlmaLinux 8.3 64-bit	Supported	Supported	Not supported
	AlmaLinux 8.4 64-bit	Supported	Supported	Not supported
	AlmaLinux 8.6 64-bit	Supported	Not supported	Not supported
	AlmaLinux 8.7	Supported	Not supported	Not supported
	AlmaLinux 9.1	Supported	Not supported	Not supported
	AlmaLinux 9.0 64-bit	Supported	Supported	Not supported
Debian	Debian 9.0.0 64-bit	Supported	Not supported	Not supported
	Debian 8.8.0 64-bit	Supported	Not supported	Not supported
	Debian 8.2.0 64-bit	Supported	Not supported	Not supported
	Debian 10.0.0 64-bit	Supported	Not supported	Not supported
	Debian 10.2.0 64-bit (Arm)	Supported	Not supported	Not supported
	Debian 10.5 64-bit	Supported	Not supported	Not supported
	Debian 10.6 64-bit	Supported	Not supported	Not supported
	Debian 11.10 64-bit	Supported	Supported	Not supported
	Debian 11.4 64-bit	Supported	Not supported	Not supported
	Debian 11.5 64-bit	Supported	Not supported	Not supported
	Debian 12.0.0 64-bit	Supported	Supported	Not supported
EulerOS	EulerOS 2.8 64-bit	Not supported	Not supported	Supported
	EulerOS 2.5 64-bit	Supported	Supported	Not supported
	EulerOS 2.3 64-bit	Not supported	Not supported	Supported
	EulerOS 2.2 64-bit	Supported	Not supported	Not supported
	EulerOS 2.8 64-bit (Arm)	Supported	Not supported	Supported
	EulerOS 2.9 64-bit	Supported	Supported	Supported
	EulerOS 2.9 64-bit (Arm)	Supported	Not supported	Not supported
	EulerOS 2.10 64-bit	Supported	Supported	Supported
Fedora	Fedora 30 64-bit	Supported	Not supported	Not supported
	Fedora 31 64-bit	Supported	Not supported	Not supported
	Fedora 36 64-bit	Supported	Not supported	Not supported
	Fedora 37 64-bit	Supported	Not supported	Not supported
	Fedora 38 64-bit	Supported	Not supported	Not supported
Huawei Cloud EulerOS	Huawei Cloud EulerOS 1.0 64-bit	Supported	Not supported	Not supported
	Huawei Cloud EulerOS 1.1 64-bit	Supported	Supported	Not supported
	Huawei Cloud EulerOS 2.0 64-bit	Supported	Supported	Supported
	Huawei Cloud EulerOS 2.0 Arm 64-bit	Supported	Supported	Supported
KylinOS	Kylin Linux Advanced Server for Kunpeng V1	Supported	Not supported	Not supported
	Kylin-Server-10-SP2-20210524-x86.iso	Supported	Not supported	Not supported
	Kylin-Server-10-SP2-20210524-arm.iso	Supported	Not supported	Not supported
openEuler	openEuler 20.03 64-bit	Supported	Not supported	Not supported
	openEuler 20.03 LTS SP3 64-bit	Supported	Not supported	Not supported
	openEuler 22.03 LTS (Arm)	Not supported	Not supported	Supported
	openEuler 22.03 LTS 64-bit	Supported	Not supported	Not supported
OpenSUSE	OpenSUSE 15.0 64-bit	Supported	Not supported	Not supported
	SUSE 15 SP5 x86	Supported	Not supported	Not supported
	SUSE 15 SP6 x86	Supported	Not supported	Not supported
Red Hat	Red Hat Linux Enterprise 6.9 64-bit	Not supported	Not supported	Supported
Red Hat	Red Hat Linux Enterprise 7.4 64-bit	Not supported	Not supported	Supported
Rocky Linux	Rocky Linux 8.4 64-bit	Supported	Supported	Not supported
	Rocky Linux 8.5 64-bit	Supported	Supported	Not supported
	Rocky Linux 8.6 64-bit	Supported	Not supported	Not supported
	Rocky Linux 9.0 64-bit	Supported	Supported	Not supported
	Rocky Linux 9.1	Supported	Not supported	Not supported
	Rocky Linux 8.7-x86	Supported	Not supported	Not supported
	Rocky Linux 9.3-x86	Supported	Not supported	Not supported
	Rocky Linux 8.7-Arm	Supported	Not supported	Not supported
Ubuntu	Ubuntu 24.04 server 64-bit	Supported	Supported	Not supported
	Ubuntu 22.04 server 64-bit	Supported	Supported	Not supported
	Ubuntu 20.04 server 64-bit	Supported	Supported	Supported
	Ubuntu 18.04 server 64-bit	Supported	Supported	Supported
	Ubuntu 18.04 server 64-bit (Arm)	Not supported	Not supported	Supported
	Ubuntu 16.04 server 64-bit	Supported	Supported	Supported
	Ubuntu 14.04 server 64-bit	Not supported	Not supported	Supported
	Ubuntu 18.04.6 server 64-bit	Supported	Not supported	Not supported
UnionTechOS	UnionTech OS Server 20 Euler (1000) 64-bit (Arm)	Supported	Not supported	Not supported
UnionTechOS	UnionTech OS-Server-20-1050e-amd64-UFU.iso	Supported	Not supported	Not supported