Overview |
Provides quick entries to common services or functions from the application or 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 to AOM 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, WeCom, 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 browsing |
The Metric Browsing page displays metric data of each resource. You can check metric values and trends, and create alarm rules for desired metrics for real-time monitoring and data correlation analysis. |
Log analysis (new) |
AOM is a unified platform for observability analysis. It does not provide log functions by itself. Instead, it integrates the log functions of Log Tank Service (LTS). You can perform operations on the AOM 2.0 or LTS console.
Log Analysis provides the following functions:
- Log management
Provides an overview, including log management, log search and analysis, and log jobs.
- Log ingestion
Ingests logs through ICAgents, cloud services, APIs, and SDKs.
- Log transfer
Transfers logs to other cloud services for long-term storage.
- Log jobs
Provides SQL scheduled jobs, function processing, and metric generation functions.
|
Log analysis (old) |
AOM allows you to search for logs, view log files, set log paths, dump logs, ingest logs to Log Tank Service (LTS), and use log streams.
- Log search
AOM enables you to quickly query logs, and locate faults based on log sources and contexts.
- Log files
You can quickly view log files of component instances or hosts to locate faults.
- Log paths
AOM can collect and display VM logs. A VM refers to an Elastic Cloud Server (ECS) running Linux.
- Log dumps
AOM enables you to dump logs to Object Storage Service (OBS) buckets for long-term storage.
- LTS access
By adding access rules, you can map logs of Cloud Container Engine (CCE), Cloud Container Instance (CCI), or custom clusters in AOM to LTS. Then you can view and analyze logs on LTS. Mapping does not generate extra fees, but duplicate mapping will.
- Log streams
Supports log search.
|
Application insights (retiring) |
Provides application monitoring, CMDB, and log ingestion. The CMDB-based application insights function will be provided by Cloud Operations Center (COC), which is in the open beta test (OBT). You are advised to use this function on COC.
- Application monitoring
An application groups identical or similar components based on service requirements. AOM supports monitoring by application.
- CMDB
You can use CMDB to centrally manage and bind resources and applications on Huawei Cloud, and provide accurate, consistent data in time for O&M.
- Log ingestion
ICAgents collect logs from hosts based on your specified collection rules, and pack and send the collected log data to AOM on a log stream basis. You can view logs on the AOM console in real time.
|
Prometheus monitoring |
Provides Prometheus instances and resource usage statistics.
- Instances
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.
|
Business monitoring (beta) |
Enables you to create log metric rules. |
Infrastructure monitoring |
Monitors workloads, clusters, processes, cloud services, and hosts.
- 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.
- 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.
- Cloud service monitoring
Service instance statuses and metric usage are displayed in line graphs and digit graphs. You can create alarm rules for monitored items.
|
Automation (Retiring) |
Provides atomic operations such as batch script execution, file distribution, and cloud service change, and allows you to customize and orchestrate atomic operations and assemble them into jobs and standard O&M processes.
Automation functions will be provided by COC, which is in the OBT. You are advised to use these functions on COC. |
Settings |
Provides service authorization, authentication, global settings, data subscription, log settings, collection settings, and menu settings.
- Service authorization
Grant the permissions to access multiple cloud services in one click.
- Authentication
Create an access code for setting API call permissions.
- Global settings
Determine whether to enable Metric Collection to collect metrics (excluding SLA and custom metrics), and TMS Tag Display to display cloud resource tags in alarm notifications to facilitate fault locating.
- Data subscription
Subscribe to metrics or alarms. After subscription, data can be forwarded to DMS topics or Webhook for retrieval.
- Log settings
You can set log quotas, delimiters, and ICAgent collection.
- Menu settings
You can choose to show or hide Overview, Application Insights, Automation, Cloud Service Monitoring, and Business Monitoring in the navigation pane of the console.
- Collection settings
You can install and manage the UniAgent, manage the ICAgent in CCE clusters centrally, manage host groups and proxy areas, and check operation logs of the UniAgent and ICAgent.
|