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 log data, and displays monitoring results in a visualized manner. In addition, automation makes routine O&M operations servitized and automated, reducing repeated operations.
This section compares AOM 1.0 with AOM 2.0.
Function |
Description |
AOM 1.0 |
AOM 2.0 |
|
---|---|---|---|---|
CMDB |
Resource retrieval |
On the homepage, search for resources (such as applications and hosts) by ID, keyword, or name. |
Not supported. |
Supported. |
Application management |
Manage the relationships between cloud service objects and applications. The "application + sub-application (optional) + component + environment" management model is used. |
|||
Resource management |
View the associations between all cloud service resource objects and applications, facilitating resource analysis and management. |
|||
Environment tags |
Add tags to created application environments so that you can quickly filter environments with the same attributes. |
|||
Resource monitoring |
Access center |
Quickly connect metrics at the business, application, middleware, and infrastructure layers for monitoring. |
Not supported. |
Supported. |
Dashboard |
Resource metrics, logs, and performance data are displayed in multiple graphs on the same screen. |
Partially supported. Only metric data and system performance data can be monitored in a visualized manner. |
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, SMS, or WeCom. |
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. |
|
Application insights |
Based on the CMDB model, the health status of resources is monitored by layer from applications, components, to environments. |
Partially supported. The CMDB model is not supported. Metric data is monitored by layer. |
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 and log data in real time, and create alarm rules for metrics to view services and analyze associated data in real time. |
Partially supported. Only metric data can be monitored and analyzed. |
Supported. |
|
Infrastructure monitoring |
The running status of hosts and cloud services, 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. |
|
Business monitoring |
ELB log data reported to LTS are extracted as metrics for unified management. This facilitates real-time monitoring on the metric browsing and dashboard pages. |
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. |
|
Data subscription |
AOM allows you to subscribe to metrics or alarms. After subscription, data can be forwarded to custom Kafka or Distributed Message Service (DMS) topics for retrieval. |
Supported. |
Supported. |
|
Collection management |
You can use UniAgents to schedule collection tasks to collect data. UniAgents can be installed manually or automatically. |
Not supported. |
Supported. |
|
Automation |
Scenarios |
Different types of tasks are provided, and cards of different atomic service scenarios can be managed. |
Not supported. |
Supported. |
Scheduled O&M |
AOM provides functions such as creating scheduled tasks, and displays execution records of scheduled tasks. |
|||
Tasks |
AOM provides functions such as task execution, and displays the execution records of all tasks. |
|||
Parameter library |
AOM provides functions such as creating parameters, and displays all existing parameter information. |
|||
Jobs |
AOM provides functions such as job creation and management. |
|||
Scripts |
AOM provides functions such as creating scripts and managing script versions. |
|||
Packages |
AOM provides functions such as creating packages and managing package versions. |
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.
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