Comparison Between AOM 1.0 and AOM 2.0

Based on AOM 1.0 functions and common application monitoring, AOM 2.0 collects and monitors more metrics and logs, and displays monitoring results in a visualized manner.

This section compares AOM 1.0 with AOM 2.0.

**Table 1** Comparison between AOM 1.0 and AOM 2.0
Function		Description	AOM 1.0	AOM 2.0
Resource monitoring	Access center	Infrastructure metrics can be quickly connected for monitoring.	Not supported.	Supported.
	Dashboard	Resource metrics and performance data are displayed in multiple graphs on the same screen.	Supported.	Supported.
	Alarm management	You can set event conditions for services or set threshold criteria for resource metrics. When an alarm is generated due to an exception in AOM or a related service, the alarm information is sent to the specified personnel by email or SMS.	Partially supported. During alarm rule creation, metrics can be selected by metric type or running Prometheus commands, but cannot be selected from full metrics.	Supported.
	Container insights	AOM monitors CCE resource usage, status, and alarms from workload and cluster dimensions for fast response and smooth workload running.	Supported.	Supported.
	Metric browsing	You can monitor metric data and trends of each resource in real time and create alarm rules for metrics to view services and analyze associated data in real time.	Supported.	Supported.
	Infrastructure monitoring	The running status of hosts, and VM CPU, memory, and disk information can be monitored in real time.	Supported.	Supported.
	Prometheus monitoring	AOM is fully interconnected with the open-source Prometheus ecosystem, monitors various components, provides multiple preset monitoring dashboards for out-of-the-box availability, and flexibly expands cloud native component metric plug-ins.	Not supported.	Supported.
	Log analysis	You can quickly search for required logs from massive quantities of logs. You can also quickly locate faults by analyzing the log source and context.	Supported.	Supported.
	Process monitoring	Rules can be set to discover deployed applications and collect associated metrics. Drill-down (from applications to components, instances, and containers) is also supported. Applications and components can be monitored from multiple dimensions.	Supported.	Supported.
Collection management	UniAgent	You can use UniAgents to schedule collection tasks to collect data. Currently, UniAgents can be installed manually or automatically.	Not supported.	Supported.

As functions of AOM 1.0 are gradually replaced by those of AOM 2.0, AOM 1.0 will be brought offline soon. You are advised to upgrade AOM 1.0 to AOM 2.0. For details, see Upgrading to AOM 2.0.

Parent topic: Service Overview

Previous topic: Application Scenarios

Next topic: Relationships Between AOM and Other Services