Manual Upgrade

Functions

• Log Upgrade

  After the upgrade, container logs and VM logs are connected to AOM 2.0. You can log in to AOM 1.0 to view historical VM logs.

• Collector Upgrade

  After the upgrade, the collector can better discover processes and automatically adapt to metric browsing functions.

• Alarm Rule Upgrade

  After the upgrade, alarm rule data is smoothly switched from AOM 1.0 to AOM 2.0, and is automatically adapted to alarm rule functions of AOM 2.0.

Log Upgrade

1. Log in to the AOM 2.0 console.
2. Ingest container and VM logs:
   • Ingestion of container logs: Choose LTS Access and ingest container logs as prompted. For details, see Adding Access Rules.
   • Ingestion of VM logs: Choose Log Ingestion and ingest VM logs as prompted. For details, see Managing Access Rules.

Collector Upgrade

1. Log in to the AOM 1.0 console.
2. In the navigation pane, choose Configuration Management > Agent Management.
3. Select Other: custom hosts from the drop-down list on the right of the page.
4. Select a host and click Upgrade ICAgent.
5. Select a target AOM 2.0 version from the drop-down list and click OK.
6. Wait for the upgrade. This process takes about one minute. When the ICAgent status changes from Upgrading to Running, the upgrade is successful.
   

   If the ICAgent is abnormal after the upgrade or if the upgrade fails, log in to the host and run the installation command again. Note that there is no need for you to uninstall the original ICAgent.

Alarm Rule Upgrade

1. Log in to the AOM 1.0 console.
2. In the navigation pane on the left, choose Alarm Center > Alarm Rules.
3. Select one or more alarm rules and click Migrate to AOM 2.0 above the rule list.
   

   • Migration cannot be undone. Exercise caution when performing this operation.
   • If the alarm rules to be migrated depend on alarm templates, these alarm templates will also be migrated.

4. In the displayed dialog box, click Confirm. The selected alarm rules will be migrated to AOM 2.0 in batches.