Help Center/ Cloud Eye/ User Guide/ Cloud Resource Monitoring/ Server Monitoring/ Cloud Eye Plug-in (Agent)/ Agent Installation and Configuration
Updated on 2025-08-07 GMT+08:00
View PDF
Share

Agent Installation and Configuration

You can install the Agent on your servers for detailed and proactive monitoring.

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 the Agent 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

  • Agent installation requires proper DNS and security group settings. If they are not correctly configured, the Agent package will fail to be downloaded. Therefore, you need to modify the DNS configuration and configure security group rules before installing the Agent.

    If the installation fails, restore the DNS configuration of the server by referring to How Do I Configure DNS and Security Groups?

  • After you install the Agent, you can click Restore Agent Configurations on the Cloud Eye console to configure the agency and files.
  • If the Agent fails to be configured by clicking Restore Agent Configurations 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. Otherwise, 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 that were 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 offers full monitoring for 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 BMS Hardware Metrics.
  • Only some Linux OSs are supported. 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.
Parent Topic: Cloud Eye Plug-in (Agent)