Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Installing an ICAgent

Updated on 2024-08-05 GMT+08:00

ICAgents collect metrics, logs, and application performance data in real time. For hosts purchased from the ECS or BMS console, you need to manually install the ICAgent. For hosts purchased from the CCE console, the ICAgent is automatically installed.

NOTE:

AOM and LTS use the same ICAgent functions. All metric data collected by ICAgents will be reported to AOM for analysis and processing. However, for logs, only those matching the latest log collection configuration in the system will be collected.

For example, if you configure log collection paths in AOM for ECSs, the previous LTS collection configurations of all ECSs under the resource set become invalid.

The following table describes the ICAgent status.

Table 1 ICAgent status

Status

Description

Running

The ICAgent is running properly.

Uninstalled

The ICAgent is not installed. For details about how to install an ICAgent, see Installing an ICAgent.

Installing

The ICAgent is being installed. This operation takes about 1 minute to complete.

Installation failed

Failed to install the ICAgent. Uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again.

Upgrading

The ICAgent is being upgraded. This operation takes about 1 minute to complete.

Upgrade failed

Failed to upgrade the ICAgent. Uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again.

Offline

The ICAgent is abnormal due to network problems. Check and restore the network.

Abnormal

The ICAgent is abnormal. Contact technical support.

Prerequisites

Before installing an ICAgent, ensure that the time and time zone of the local browser are consistent with those of the server. If multiple servers are deployed, ensure that the local browser and multiple servers use the same time zone and time. Otherwise, metric data of applications and servers displayed on the UI may be incorrect.

Installation Methods

There are two methods to install an ICAgent. Note that the two methods are not applicable to container nodes created through ServiceStage or CCE. For container nodes, you do not need to manually install an ICAgent. Instead, you only need to perform certain operations when creating clusters or deploying applications.

For details, see Table 2.

Table 2 Installation methods

Method

Scenario

Initial installation

This method is used when the following condition is met:

An ICAgent has never been installed on your server.

Inherited installation

This method is used when the following conditions are met:

You need to install ICAgents on multiple servers. An ICAgent has been installed on one of the servers. All the servers are in the same VPC. If the servers are not in the same VPC, bind EIPs to them before using this installation method.

Initial Installation

After you apply for a server and install an ICAgent for the first time, perform the following operations:

  1. Obtain an Access Key ID/Secret Access Key (AK/SK).

    • If you have obtained the AK/SK, skip this step.
    • If you have not obtained an AK/SK, obtain them first.

  2. In the navigation pane, choose Configuration Management > Agent Management.
  3. Select Other: custom hosts, and click Install ICAgent.
  4. Click Copy Command to copy the installation command.
  5. Use a remote login tool to log in to the target server as the root user, and run the following command to disable historical record collection:

    set +o history

  6. Run the copied installation command and enter the obtained AK and SK as prompted.
  7. After the ICAgent is installed, run the following command to enable historical record collection:

    set -o history
    NOTE:
    • If the message ICAgent install success is displayed, the ICAgent has been installed in the /opt/oss/servicemgr/ directory. After the ICAgent has been installed, choose Configuration Management > Agent Management to view the ICAgent status.
    • If the ICAgent fails to be installed, uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again. If the problem persists, contact technical support.

Inherited Installation

If an ICAgent has been installed on a server and the ICProbeAgent.zip installation package exists in the /opt/ICAgent/ directory of this server, use this method to install an ICAgent on a remote server with a few clicks.

  1. Run the following command (x.x.x.x indicates the server IP address) on the server where an ICAgent has been installed:

    bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -ip x.x.x.x

  2. Enter the password of the root user as prompted.

    NOTE:
    • Inherited installation is not supported when ICAgents are installed using an IAM agency.
    • If both the expect tool and the ICAgent have been installed on the server, an ICAgent will be installed on the remote server after the preceding command is executed. If an ICAgent has been installed on the server, but the Expect tool has not, enter the information as prompted for installation.
    • Ensure that the root user can run the SSH or SCP command on the server where an ICAgent has been installed to remotely communicate with the server where an ICAgent is to be installed.
    • If the message ICAgent install success is displayed, the ICAgent has been installed in the /opt/oss/servicemgr/ directory. After the ICAgent has been installed, choose Configuration Management > Agent Management to view the ICAgent status.
    • If the ICAgent fails to be installed, uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again. If the problem persists, contact technical support.

Inherited Batch Installation

If an ICAgent has been installed on a server and the ICProbeAgent.zip installation package exists in the /opt/ICAgent/ directory of this server, use this method to install ICAgents on multiple remote servers with a few clicks.

NOTICE:
  1. Ensure that you can run the SSH and SCP commands on the server where an ICAgent has been installed to communicate with the remote servers where an ICAgent is to be installed.
  2. If you have installed an ICAgent in a server through an agency, you also need to set an agency for other servers where an ICAgent is to be installed.
  3. Batch installation scripts depend on Python versions. You are advised to implement batch installation on hosts running Python 3.x.
  4. Press Enter at the end of each line in the iplist.cfg file.

Prerequisites

The IP addresses and passwords of all servers on which an ICAgent is to be installed have been collected, sorted in the iplist.cfg file, and uploaded to the /opt/ICAgent/ directory on the server where an ICAgent has been installed. The following is an example of the iplist.cfg file, where IP addresses and passwords are separated by spaces.

192.168.0.109 password (Set the password as required.)

192.168.0.39 password (Set the password as required.)

NOTE:
  • Because the iplist.cfg file contains sensitive information, you are advised to clear the information in time.
  • If the passwords of all servers are the same, list IP addresses in the iplist.cfg file and enter the password during execution. If the password of an IP address is different from those of other IP addresses, enter the password next to this IP address.
  • Batch installation depends on Python 3.x. If the system displays a message indicating that Python cannot be found during the installation, install Python and try again.
  • Before the installation, check whether the Python command file exists. If the file does not exist, create a soft link.

Procedure

  1. Run the following command on the server where an ICAgent has been installed:

    bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -batchModeConfig /opt/ICAgent/iplist.cfg

    Enter the preset password of the root user as prompted. If the passwords of all IP addresses have been configured in the iplist.cfg file, press Enter to skip this step. Otherwise, enter the preset password.

    batch install begin
    Please input default passwd:
    send cmd to 192.168.0.109
    send cmd to 192.168.0.39
    2 tasks running, please wait...
    2 tasks running, please wait...
    2 tasks running, please wait...
    End of install agent: 192.168.0.39
    End of install agent: 192.168.0.109
    All hosts install icagent finish.

    Wait until the message All hosts install icagent finish. is displayed, which indicates that the ICAgent has been installed on all the hosts listed in the configuration file.

  2. After the ICAgent has been installed, choose Configuration Management > Agent Management to view the ICAgent status.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback