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

Introduction

Application Operations Management (AOM) is a one-stop, multi-dimensional O&M management platform for cloud applications. It provides one-stop observability analysis and automated O&M solutions. By collecting metrics, logs, and performance data from the cloud and local devices, AOM enables you to monitor real-time running status of applications, resources, and services and detect faults in a timely manner, improving O&M automation capability and efficiency.

Table 1 Function description

Category

Description

Overview

Provides quick entries to common services or functions from the container perspective, and monitors and displays key resource or application data in real time.

Access center

At the access center, you can quickly connect multi-dimensional metrics at different layers in various scenarios. After the connection is complete, you can view the usage of metrics and status of related resources or applications on the Metric Browsing page.

Dashboard

With a dashboard, different resource data graphs can be displayed on the same screen. Various graphs (such as line graphs, digit graphs, and status graphs) help you monitor data comprehensively.

Alarm management

Provides the alarm list, event list, alarm rules, alarm templates, and alarm notifications.

  • Alarm list

    Alarms are reported when AOM or an external service is abnormal or may cause exceptions. You need to take measures accordingly. Otherwise, service exceptions may occur.

    The alarm list displays the alarms generated within a specified time range.

  • Event list

    Events generally carry some important information, informing you of the changes of AOM or an external service. Such changes do not necessarily cause exceptions.

    The event list displays the events generated within a specified time range.

  • Alarm rules

    By setting alarms rules, you can define event conditions for services or threshold conditions for resource metrics. An event alarm is generated when the resource data meets the event condition. A threshold-crossing alarm is generated when the metric data of a resource meets the threshold condition and an insufficient data event is generated when no metric data is reported, so that you can discover and handle exceptions at the earliest time.

  • Alarm templates

    An alarm template is a combination of alarm rules based on cloud services. You can use an alarm template to create threshold alarm rules, event alarm rules, or PromQL alarm rules for multiple metrics of one cloud service in batches.

  • Alarm notification

    AOM supports alarm notification. You can configure alarm notification by creating alarm action rules and noise reduction rules. When an alarm is generated due to an exception in AOM or an external service, the alarm information is sent to specified personnel by email or Short Message Service (SMS). In this way, related personnel can take measures to rectify faults in a timely manner to avoid service loss.

Metric analysis

Provides metric browsing, Prometheus monitoring, and resource usage.

  • Metric browsing

    The Metric Browsing page displays metric data of each resource. You can monitor metric values and trends in real time, and create alarm rules for desired metrics. In this way, you can monitor services in real time and perform data correlation analysis.

  • Prometheus monitoring

    AOM is fully connected with the open-source Prometheus ecosystem. It monitors many types of components, provides multiple ready-to-use dashboards, and supports flexible expansion of cloud-native component metric plug-ins.

  • Resource usage

    After metric data is reported to AOM through Prometheus monitoring, you can view the number of reported basic and custom metric samples on the Resource Usage page.

Log analysis (beta)

Supports log search.

AOM enables you to quickly query logs, and locate faults based on log sources and contexts.

Container insights

Monitors workloads and clusters.

  • Workload monitoring

    Workloads deployed on CCE are monitored. Therefore, you can understand the resource usage, status, and alarms of workloads in a timely manner.

  • Cluster monitoring

    Clusters deployed using CCE are monitored. The Cluster Monitoring page displays the pod status and CPU usage of the clusters in real time.

Infrastructure monitoring

Provides host monitoring.

  • Host monitoring

    Host monitoring displays resource usage, trends, and alarms, so that you can quickly respond to malfunctioning hosts and handle errors to ensure smooth host running.

Process monitoring

Provides application and component monitoring, and application discovery.

  • Application monitoring

    An application groups identical or similar components based on service requirements.

  • Component monitoring

    Components refer to the services that you deploy, including containers and common processes.

  • Application discovery

    AOM can discover applications and collect their metrics based on configured rules.

Collection management

Centrally manages the life cycle of collection plug-ins and delivers instructions (such as script delivery and execution). UniAgent does not collect data; instead, collection plug-ins do that.

Management

Provides global configuration.

  • Global configuration

    Includes cloud service authorization, access management, and global settings.

Going Back to AOM 1.0

On any page of AOM 2.0, click Back to 1.0 in the navigation pane to go back to AOM 1.0. For details about AOM 1.0, see AOM 1.0 User Guide.

Enterprise Project

An enterprise project can contain one or more applications.

Log in to the AOM 2.0 console. In the enterprise project drop-down list in the navigation pane, select a desired enterprise project.

To use the enterprise project function, contact engineers.