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

Installing and Configuring the Agent

You can install the Agent on your servers to enable proactive, system-level monitoring with fine-grained metrics.

Based on the OS you are going to use, server quantity, and personal habits, install the Agent by choosing one or more of the following scenarios:

Scenario

Service

Reference

Automatically Installing Agents on All Servers

ECS

Automatically Installing Agents on All Servers

Automatically Installing Agents on Selected Servers

ECS

Customizing the Automatic Agent Installation

Installing the Agent on a Single Server

ECS and BMS

Installing the Agent on a Single Server

Manually Installing the Agents in Batches

ECS

Manually Installing the Agents in Batches

Configuration Dependencies

  • Before installing the Agent, click Configure on the Server Monitoring page of the Cloud Eye console in the desired region. The system will automatically grant temporary AK/SK authorization to the Agent installed on all ECSs or BMSs in the region. New resources created in this region will automatically obtain this authorization.
  • Agent installation requires proper DNS and security group settings. If they are not correctly configured, the Agent package will fail to be downloaded. Therefore, ensure your DNS settings and security group rules are correct before installing the Agent. For details, see Checking/Modifying the DNS and Security Group Configurations.
  • If the Agent fails to be configured by clicking Configure or due to other reasons, manually configure it.
  • To check the OSs supported by the Agent, see What OSs Does the Agent Support?
  • You are advised to use an ECS or BMS which has installed an Agent to create a private image and create an ECS or BMS from the image.
    • A private image created in one region cannot be used in another region. If used, no monitoring data will be generated for the servers created from that private image.
    • Cloud Eye does not provide technical support for Agent installation issues on servers created from private images.

BMS Hardware Monitoring Plug-in

Agent 2.5.6.1 and later enhanced versions integrate the BMS hardware monitoring plug-in. The plug-in checks hardware health in real time, identifies potential issues early, and detects all BMS hardware faults.

If a BMS does not have the hardware monitoring plug-in, Cloud Eye cannot detect the hardware fault in a timely manner, which may affect service availability. In addition, you need to contact technical support to rectify the fault.

After the hardware monitoring plug-in is installed, you will be notified of potential hardware issues through event notifications. You need to authorize the BMS to repair or replace the risky hardware in a timely manner.

  • The hardware monitoring plug-in only collects some necessary OS metrics to identify hardware faults. For details, see What Are BMS Hardware Metrics?
  • Only some Linux OSs support the hardware monitoring plug-in. For details, see What OSs Does the Agent Support?
  • BMSs of all specifications support the hardware monitoring plug-in.
  • If your BMS uses a private image as the OS, ensure that the image has the following software installed: dmidecode, lscpu, dmesg, lspci, modinfo, ifconfig, ethtool, hinicadm, smartctl, lsscsi, and uname.