Managing ICAgent in Container Scenarios
ICAgent is a log collection tool for LTS. It runs on hosts where logs need to be collected. This section describes how to install ICAgent on a host, upgrade ICAgent, uninstall ICAgent, check the ICAgent version description, and check the ICAgent status.
Container scenarios cover services deployed on Kubernetes container platforms , such as those deployed in CCE clusters, self-built Kubernetes clusters, and ServiceStage containers.
Installing ICAgent
- Installing ICAgent in a CCE cluster
Currently, ICAgent can be installed only in CCE standard and Turbo clusters. You cannot install ICAgent in CCE Autopilot or Agile clusters.
- Choose Host Management > Hosts in the navigation pane.
- Click the CCE Cluster tab. Select ICAgent Status in the search box to filter clusters whose ICAgent is in Uninstalled state, select one of the clusters, and click Upgrade ICAgent.
Figure 1 Upgrading ICAgent in a CCE cluster
- If no CCE cluster is displayed on the Hosts page, you need to authorize LTS to access AOM 2.0. Log in to the AOM 2.0 console and grant AOM 2.0 permissions to access cloud services, such as LTS and CCE. For details, see Authorizing AOM to Access Other Cloud Services.
- If there are no CCE clusters available, Output to AOM is unavailable.
- To disable the function of collecting container standard output to AOM 1.0, ICAgent 5.12.133 or later is required.
- When a CCE cluster is created, ICAgent is installed on its hosts by default and reports logs to LTS. The Output to AOM feature is disabled by default. If you enabled Output to AOM after cluster creation but want to switch back to reporting logs to LTS, ensure Output to AOM is disabled before upgrading ICAgent. For Ingesting CCE Application Logs to LTS, you are advised to collect container standard output to LTS instead of AOM.
If Output to AOM is enabled, LTS will charge you based on the actual log traffic. For details, see LTS Pricing Details.
- CCE cluster ID: Each cluster has a fixed ID.
- When ICAgent is upgraded, LTS automatically creates a log group and host group for your CCE cluster, named k8s-log-{Cluster ID}. You can ingest logs of this CCE cluster to this log group when creating an ingestion configuration. For details, see Ingesting CCE Application Logs to LTS.
- If the cluster's hosts do not have ICAgent installed or have an outdated version, clicking Upgrade ICAgent will install or upgrade ICAgent on all hosts in the cluster.
- In the displayed dialog box, click OK.
The ICAgent upgrade takes about 1 minute. When the ICAgent status changes from Updating to Running, the upgrade is successful.
Figure 2 Upgrading ICAgent
- Installing ICAgent in a self-built Kubernetes cluster: For details, see Install the Log Collection Component.
In this installation mode, the cluster size is limited to a maximum of 50 nodes and 400 pods.
Upgrading ICAgent
Upgrading ICAgent in a CCE cluster is the same as the installation process. For details, see Installing ICAgent in a CCE cluster.
Uninstalling ICAgent

If ICAgent is uninstalled from a host, log collection will be affected. Exercise caution when performing this operation.
Uninstalling ICAgent does not delete the installation files. You need to delete them manually if necessary.
For container scenarios, see Managing UniAgents and ICAgents in CCE Clusters.
Checking the ICAgent Status
To check the ICAgent status of a target host, choose Host Management > Hosts in the navigation pane, and click the CCE Cluster tab. For status details, see Table 1.
Status |
Description |
---|---|
Running |
ICAgent is running properly. |
Uninstalled |
ICAgent is not installed. |
Installing |
ICAgent is being installed. This process takes about 1 minute. |
Installation failed |
ICAgent installation failed. |
Upgrading |
ICAgent is being upgraded. This process takes about 1 minute. |
Upgrade failed |
ICAgent upgrade failed. |
Offline |
ICAgent is abnormal because the AK/SK is incorrect. Obtain the correct AK/SK and install ICAgent again. |
Faulty |
ICAgent is faulty. Contact technical support. |
Uninstalling |
ICAgent is being uninstalled. This process takes about 1 minute. |
Authentication error |
Authentication fails because parameters were incorrectly configured during ICAgent installation. |
Checking the ICAgent Version
To check the ICAgent version of a target host, choose Host Management > Hosts in the navigation pane, and click the CCE Cluster tab. You are advised to upgrade ICAgent to the latest version as soon as possible. For version details, see Table 2.
Version |
Description |
Released |
---|---|---|
7.3.6 |
|
2025-07-25 |
7.3.3 |
|
2025-06-26 |
7.3.2 |
Resolved the issue where ICAgent-reported system logs cannot be queried by cluster name on the AOM 1.0 console in self-built Kubernetes scenarios. |
2025-06-09 |
7.3.1 |
|
2025-05-26 |
7.2.6 |
Improved the AgentId file clearance logic for ICAgent re-installation and uninstallation on ECSs, resolving the issue of AgentId duplication after ICAgent is pre-installed in private images. |
2025-05-14 |
7.2.4 |
Adjusted the cursor directory structure. Cursor file names no longer include log group or log stream paths, and cursor files now stored directly in their corresponding directories. |
2025-04-25 |
7.2.2 |
|
2025-03-13 |
7.2.1 |
|
2025-02-28 |
7.1.22 |
Optimized the code to reduce the memory consumed for obtaining pod information. |
2025-01-23 |
7.1.19 |
|
2025-01-13 |
7.1.17 |
Optimized the log collection process to adjust the size of transmitted blocks. |
2025-01-03 |
7.1.14 |
|
2024-12-25 |
7.1.12 |
Solved the issue where, in some scenarios, CPU usage increased due to timer leakage caused by the Go version. |
2024-12-15 |
7.1.6 |
|
2024-11-21 |
7.1.5 |
Solved the issue that logs continued to be collected after all configurations in a project are deleted or disabled. |
2024-11-21 |
7.1.3 |
Optimized the httpclient component's performance in log sending. |
2024-11-02 |
7.1.1 |
Optimized the ICAgent architecture and unified the Agents of AOM 1.0 and AOM 2.0. |
2024-10-26 |
5.12.233 |
|
2024-10-17 |
5.12.232 |
|
2024-10-14 |
5.12.231 |
|
2024-10-11 |
5.12.230 |
|
2024-10-09 |
5.12.224 |
Cleared all export HISTSIZE=0 entries (if any) from the .bashrc file in the ECS upgrade scenario. |
2024-09-27 |
5.12.218 |
|
2024-09-26 |
5.12.185 |
|
2024-05-20 |
5.12.184 |
|
2024-05-16 |
5.12.183 |
Optimized the wrapping files for the container standard output of containerd nodes. |
2024-05-11 |
5.12.182 |
Solved the syslog switch issue. |
2024-04-28 |
5.12.181 |
|
2024-04-25 |
5.12.177 |
Solved the infinite loop issue of wrapping. |
2024-03-28 |
5.12.176 |
|
2024-03-18 |
5.12.175 |
Solved the collection performance bottleneck issue of structured logs. |
2024-03-13 |
5.12.172 |
Optimized the supported wrapping mode. |
2024-02-28 |
5.12.171 |
Solved the JSON parsing issue (not deleting escape characters) of standard output logs of Docker nodes. |
2024-01-31 |
5.12.170 |
|
2024-01-29 |
5.12.166 |
|
2023-12-27 |
5.12.165 |
Added the function of obtaining the initial agent ID from the configuration file. If the agent ID does not meet the verification requirements, the randomly generated UUID is used. |
2023-12-21 |
5.12.163 |
Supported ICAgent installation using the UniAgent plug-in. |
2023-12-13 |
5.12.159 |
|
2023-11-27 |
5.12.158 |
Solved the issue that memory leakage of container metrics caused ICAgent restart when the metric switch was turned off. |
2023-11-08 |
5.12.157 |
|
2023-11-06 |
5.12.156 |
Solved the issue of obtaining the installation package from OBS and changed the protocol from HTTP to HTTPS. |
2023-11-01 |
5.12.154 |
Supported log structuring. |
2023-10-31 |
5.12.150 |
|
2023-10-17 |
5.12.149 |
Supported mounting wrapping. |
2023-10-12 |
5.12.148 |
Solved the high CPU usage issue in the multi-GPU scenario. |
2023-08-30 |
5.12.147 |
Solved the issue that log transfer function could not be restarted and the host GPU metric adaptation issue. |
2023-08-17 |
5.12.142 |
Supported the collection of container GPU metrics of CCE clusters of v1.25 or later. |
2023-06-13 |
5.12.139 |
Solved the issue of a large number of TIME_WAIT TCP connections when LTS logs are reported. |
2023-04-25 |
5.12.135 |
|
2023-02-08 |
5.12.133 |
Supported multi-line collection of container standard output logs. |
2022-12-17 |
5.12.130 |
Supported direct ingestion of CCE logs to LTS. |
2022-11-04 |
5.12.120 |
|
2022-08-28 |
5.12.111 |
Added thread metrics and fixed the issue that the LVS disk partition metrics fail to be obtained. |
2022-06-09 |
5.12.100 |
|
2022-01-15 |
5.12.98 |
Supported LTS log collection blacklists and changed the source of container metrics to working_set. |
2021-09-29 |
5.12.96 |
Supported discovery of more types of cloud resources. |
2021-09-22 |
5.12.90 |
Updated the GPU metric source. |
2021-07-15 |
5.12.87 |
Supported more types of disks. |
2021-03-30 |
5.12.75 |
Adapted to secure containers. |
2021-03-09 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot