2020-12-31
|
This issue is the first official release.
|
diff --git a/docs/aom/umn/aom_02_1012.html b/docs/aom/umn/aom_02_1012.html
deleted file mode 100644
index d7b2363a..00000000
--- a/docs/aom/umn/aom_02_1012.html
+++ /dev/null
@@ -1,81 +0,0 @@
-
-
-What Can I Do If Resources Are Not Running Properly?
-Resource statuses include Normal, Warning, Abnormal, Deleted, and Silent. Warning, Abnormal, and Silent indicate improper resource running. Analyze and rectify faults according to the following instructions.
-
Warning
If a minor alarm or warning exists, the resource status is Warning.
-
Suggestion: Handle the alarm based on alarm details.
-
-
Abnormal
If a critical or major alarm exists, the resource status is Abnormal.
-
Suggestion: Handle the alarm based on alarm details.
-
-
Silent
If the ICAgent fails to collect resource metrics, the resource status is Silent. The causes include but are not limited to:
-
- Cause 1: The ICAgent is abnormal.
Suggestion: In the navigation pane, choose Agent Management. On the page that is displayed, check the ICAgent status, as shown in Figure 1. If the status is not Running, the ICAgent has been uninstalled or is abnormal. For details on how to solve the problem, see Table 1.
-
-Table 1 ICAgent troubleshooting suggestionsStatus
- |
-Suggestion
- |
-
|---|
-
-Uninstalled
- |
-Install the ICAgent by referring to Installing the ICAgent.
- |
-
-Installing
- |
-Wait for about 1 minute to complete the ICAgent installation.
- |
-
-Installation failed
- |
-If the ICAgent fails to be installed, reinstall it.
- |
-
-Upgrading
- |
-Wait for about 1 minute to complete the ICAgent upgrade.
- |
-
-Upgrade failed
- |
-If the ICAgent fails to be upgraded, reinstall it.
- |
-
-Offline
- |
-Check for network faults and rectify such faults.
- |
-
-Faulty
- |
-Contact technical support.
- |
-
-
-
-
Figure 1 Checking the ICAgent status
-
-
- Cause 2: AOM cannot monitor the current resource.
Suggestion: Check whether your resources can be monitored by AOM. AOM can monitor hosts, Kubernetes containers, and user processes, but does not monitor system processes.
- - Cause 3: The local time of the host is not synchronized with the NTP server time.
NTP Sync Status: indicates whether the local time of the host is synchronized with the NTP server time. The value can be 0 or 1. 0 indicates the synchronized status while 1 indicates the asynchronized status.
-
Suggestion: Choose View Management > Metric Monitoring and check the NTP Sync Status metric of the host. If the value of NTP Sync Status is 1, the local time of the host is not synchronized with that of the NTP server. To solve the problem, perform synchronization.
- - Cause 4: The resource is deleted or stopped.
Suggestions:
-- On the ECS page, check whether the host is restarted, stopped, or deleted.
- On the Cloud Container Engine (CCE) page, check whether the component is stopped or deleted.
-
-
-
Data Subscription
+AOM allows you to subscribe to metrics or alarms. After the subscription, data can be forwarded to custom Kafka or Distributed Message Service (DMS) topics for you to retrieve.
+
A maximum of 10 data subscription rules can be created.
+
+
Creating Subscription Rules
- Log in to the AOM console. In the navigation pane, choose Configuration Management > Data Subscription.
- Click Create Subscription Rule in the upper right corner. On the displayed page, set parameters and click OK.
You can set Subscription Target Type to Custom Kafka or DMS as required.
+- If Subscription Target Type is set to Custom Kafka, set parameters based on Table 1.
+
Table 1 Subscription rule parametersParameter
+ |
+Description
+ |
+Example
+ |
+
|---|
+
+Rule Name
+ |
+Subscription rule name.
+ |
+Enter aom-kafka-test.
+ |
+
+Subscription Content
+ |
+Options: Metric and Alarm.
+ |
+Select Metric.
+ |
+
+Subscription Target Type
+ |
+Options: Custom Kafka and DMS.
+ |
+Select Custom Kafka.
+ |
+
+Subscription Target Address
+ |
+Custom Kafka address, which needs to be connected to Internet.
+Each address must be in the format of "IPv4 address:port". If multiple addresses exist, separate them by commas (,). Example: 192.168.0.1:9092,192.168.0.2:9092
+ |
+Set this parameter as required.
+ |
+
+
+
+
- (Optional) On the Rule Details page, click
to enable Kafka SASL_SSL and set parameters based on Table 2. AOM supports only Kafka SASL_SSL security authentication. If you have enabled Kafka SASL_SSL for instances, you also need to enable it on the Rule Details page.
+
+
+Table 2 Setting Kafka SASL_SSL parametersParameter
+ |
+Description
+ |
+Example
+ |
+
|---|
+
+User name
+ |
+SASL username for instance access authentication.
+ |
+demo
+ |
+
+Password
+ |
+SASL password for instance access authentication. Keep your password secure. The system cannot detect your password.
+ |
+-
+ |
+
+Client certificate
+ |
+Use a client certificate in .pem format.
+ |
+-
+ |
+
+
+
+
- Click Verify and Save Custom Kafka Configuration to verify the connectivity of the custom Kafka instance.
- Select a topic for transmitting data and click OK.
+ - If Subscription Target Type is set to DMS, set parameters based on Table 3.
+
Table 3 Subscription rule parametersParameter
+ |
+Description
+ |
+Example
+ |
+
|---|
+
+Rule Name
+ |
+Subscription rule name.
+ |
+Enter aom-kafka-test.
+ |
+
+Subscription Content
+ |
+Options: Metric and Alarm.
+ |
+Select Metric.
+ |
+
+Subscription Target Type
+ |
+Options: Custom Kafka and DMS.
+ |
+Select DMS.
+ |
+
+Instance
+ |
+Select a DMS instance. If no DMS instance is available, click Create DMS Instance to create one.
+ |
+Select kafka-aom-7160.
+ |
+
+
+
+
- On the Rule Details page, click Create a network connection channel.
- Verify the DMS instance connectivity.
Ensure that an inbound rule is added to allow traffic from source IP address 198.19.128.0/20 on port 9011. To set a security group rule, do as follows:
+- Log in to the management console.
- Click
in the upper left corner and choose Networking > Virtual Private Cloud. - In the navigation pane, choose Access Control > Security Groups. Then, locate the security group corresponding to the DMS instance and click Manage Rule in the Operation column.
- On the Inbound Rules tab page, click Add Rule to allow the network traffic from source IP address 198.19.128.0/20 on port 9011.
+ - Click Verify and Save DMS Configuration Information.
- Select a topic for transmitting data and click OK.
+
+
+
+
Data Subscription Format
- Metric data example (in JSON format)
package metric
+
+type MetricDatas struct {
+ Metrics []Metrics `json:"metrics"`
+ ProjectId string `json:"project_id"`
+}
+
+type Metrics struct {
+ Metric Metric `json:"metric"`
+ Values []Value `json:"values"`
+ CollectTime int64 `json:"collect_time"`
+}
+
+type Metric struct {
+ Namespace string `json:"namespace"`
+ Dimensions []Dimension `json:"dimensions"`
+}
+
+type Value struct {
+ Value interface{} `json:"value"`
+ Type string `json:"type"`
+ Unit string `json:"unit"`
+ StatisticValues string `json:"statisticvalues"`
+ MetricName string `json:"metric_name"`
+}
+
+type Dimension struct {
+ Name string `json:"name"`
+ Value string `json:"value"`
+}
+
+ - Kafka message example
key:,
+value:{"metrics":[{"metric":{"namespace":"PAAS.NODE","dimensions":[{"name":"nodeName","value":"test-vss-cop-master-1"},{"name":"nodeIP","value":"1.1.1.1"},{"name":"hostID","value":"75d97111-4734-4c6c-ae9e-f6111111111"},{"name":"nameSpace","value":"default"},{"name":"clusterId","value":"46a7bc0d-1d8b-11ea-9b04-333333333333333"},{"name":"clusterName","value":"test-vss-111"},{"name":"diskDevice","value":"vda"},{"name":"master","value":"true"}]},"values":[{"value":0,"type":"","unit":"Kilobytes/Second","statisticvalues":"","metric_name":"diskReadRate"},{"value":30.267,"type":"","unit":"Kilobytes/Second","statisticvalues":"","metric_name":"diskWriteRate"}],"collect_time":1597821030037}],"project_id":"111111111111111111111"}
+ - Alarm data format
Example:
+{
+ "events": [{
+ "id": "4346299651651991683",
+ "starts_at": 1597822250194,
+ "ends_at": 0,
+ "arrives_at": 1597822250194,
+ "timeout": 300000,
+ "resource_group_id": "312313123112222222222232131312131",
+ "metadata": {
+ "kind": "Pod",
+ "event_severity": "Major",
+ "resource_type": "service",
+ "clusterId": "6add4ef5-1358-11ea-a5bf-111111111",
+ "event_type": "alarm",
+ "clusterName": "cce-ief-4516140c-96ca-4a5f-8d85-1111111",
+ "namespace": "PAAS.NODE",
+ "name": "test15769793809553052-f5557bd7f-qnfkm",
+ "event_name": "FailedScheduling",
+ "resource_id": "clusterName=cce-ief-4516140c-96ca-4a5f-8d85-111111;clusterID=6add4ef5-1358-11ea-a5bf-11111111111;kind=Pod;namespace=30d5758f166947c6b164af604a654b09;name=test15769793809553052-f5557bd7f-qnfkm;uid=589fc746-245d-11ea-a465-fa163e5fc15d",
+ "nameSpace": "30d5758f166947c6b164af604a654b09",
+ "resource_provider": "CCE",
+ "nodeID": "589fc746-245d-11ea-a465-fa163e5fc15d"
+ },
+ "annotations": {
+ "alarm_probableCause_zh_cn": "FailedScheduling",
+ "alarm_probableCause_en_us": "FailedScheduling",
+ "message": "0/110 nodes are available: 1 node(s) had taints that the pod didn't tolerate, 109 node(s) didn't match node selector."
+ },
+ "attach_rule": {
+
+ }
+ }],
+ "project_id": "312313123112222222222232131312131"
+}
+Parameter description:
+
+Table 4 Alarm parametersParameter
+ |
+Type
+ |
+Description
+ |
+
|---|
+
+events
+ |
+Array of objects. For details, see Table 5.
+ |
+Event or alarm details.
+ |
+
+project_id
+ |
+String
+ |
+Project ID obtained from IAM. Generally, a project ID contains 32 characters.
+ |
+
+
+
+
Table 5 EventModelParameter
+ |
+Type
+ |
+Description
+ |
+
|---|
+
+id
+ |
+String
+ |
+Event or alarm ID, which is automatically generated by the system.
+ |
+
+starts_at
+ |
+Long
+ |
+Time when an event or alarm is generated. The value is a China Standard Time (CST) timestamp precise down to the millisecond.
+ |
+
+ends_at
+ |
+Long
+ |
+Time when an event or alarm is cleared. The value is a CST timestamp precise down to the millisecond. If the value is 0, the event or alarm is not deleted.
+ |
+
+arrives_at
+ |
+Long
+ |
+Time when an event or alarm reaches AOM. The value is a CST timestamp precise down to the millisecond.
+ |
+
+timeout
+ |
+Long
+ |
+Duration (unit: ms) at which an alarm is automatically cleared. For example, if the duration is one minute, set this parameter to 60000. The default duration is three days.
+ |
+
+resource_group_id
+ |
+String
+ |
+Reserved field for a resource group. The default value is the same as the value of projectid.
+ |
+
+metadata
+ |
+Object
+ |
+Details of an event or alarm. The value is a key-value pair. The following fields are mandatory:
+- event_name: Event or alarm name, which is a string.
- event_severity: Event severity, which is an enumerated value with the string-type attribute. Options: Critical, Major, Minor, and Info.
- event_type: Event type, which is an enumerated value with the string-type attribute. Options: event and alarm.
- resource_provider: Name of a cloud service corresponding to an event, which is a string.
- resource_type: Resource type corresponding to an event, which is a string.
- resource_id: Resource ID corresponding to an event, which is a string.
+ |
+
+annotations
+ |
+Object
+ |
+Additional field for an event or alarm, which can be left blank.
+ |
+
+attach_rule
+ |
+Object
+ |
+Reserved field for an event or alarm, which can be left blank.
+ |
+
+
+
+
+
+
Follow-up Operations
After the data subscription rule is created, AOM will send data to your custom Kafka or DMS topic so that you can retrieve the subscribed metrics or alarms.
+
+
Metric Description
-
-
-
diff --git a/docs/aom/umn/aom_02_1015.html b/docs/aom/umn/aom_02_1015.html
deleted file mode 100644
index 6dad0a50..00000000
--- a/docs/aom/umn/aom_02_1015.html
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-Introduction
-Metrics reflect resource performance data or status. A metric consists of the namespace, dimension, name, and unit. Metrics are classified into system metrics and custom metrics.
-
- System metrics: basic metrics provided by AOM, such as CPU usage and used CPU cores.
- Custom metrics: self-defined metrics. Custom metrics can be reported using the following methods:
- Method 1: Use the AOM API for reporting monitoring data.
- Method 2: Connect to the Prometheus platform when creating container applications on Cloud Container Engine (CCE).
-
-
Metric Namespaces
Metric namespaces indicate containers for storing metrics. Metrics in different namespaces are independent of each other so that metrics of different applications will not be aggregated to the same statistics information.
-
- Namespaces of system metrics cannot be changed. These namespaces must start with PAAS., as shown in Table 1.
-
Table 1 Namespaces of system metricsNamespace
- |
-Description
- |
-
|---|
-
-PAAS.AGGR
- |
-Namespace of cluster metrics
- |
-
-PAAS.NODE
- |
-Namespace of host, network, disk, and file system metrics
- |
-
-PAAS.CONTAINER
- |
-Namespace of service, instance, process, and container metrics
- |
-
-
-
-
-
- Namespaces of custom metrics must be in the XX.XX format (excluding PAAS.XX, SYS.XX, or SRE.XX). Each namespace must be 3 to 32 characters long and start with a letter. Only digits, uppercase letters, lowercase letters, and underscores (_) are allowed. For example, aom.host_01.
-
-
Metric Dimensions
Metric dimensions indicate the categories of metrics. Each metric has certain features, and a dimension may be considered as a category of relevant features.
-
-
-
Network Metrics and Dimensions
-
-
Table 1 Network metricsMetric
- |
-Description
- |
-Value Range
- |
-Unit
- |
-
|---|
-
-Downlink rate (recvBytesRate)
- |
-Inbound network traffic rate of a measured object
- |
-≥ 0
- |
-Byte per Second (BPS)
- |
-
-Downlink rate (recvPackRate)
- |
-Number of data packets received by the NIC per second
- |
-≥ 0
- |
-Packet per Second (PPS)
- |
-
-Downlink error rate (recvErrPackRate)
- |
-Number of error packets received by the NIC per second
- |
-≥ 0
- |
-PPS
- |
-
-Uplink rate (sendBytesRate)
- |
-Outbound network traffic rate of a measured object
- |
-≥ 0
- |
-BPS
- |
-
-Uplink error rate (sendErrPackRate)
- |
-Number of error packets sent by the NIC per second
- |
-≥ 0
- |
-PPS
- |
-
-Uplink rate (sendPackRate)
- |
-Number of data packets sent by the NIC per second
- |
-≥ 0
- |
-PPS
- |
-
-Total rate (totalBytesRate)
- |
-Total inbound and outbound network traffic rate of a measured object
- |
-≥ 0
- |
-BPS
- |
-
-
-
-
-
-
Table 2 Dimensions of network metricsDimension
- |
-Description
- |
-
|---|
-
-clusterId
- |
-Cluster ID
- |
-
-clustername
- |
-Cluster name
- |
-
-NIC
- |
-Network interface card (NIC)
- |
-
-hostID
- |
-Host ID
- |
-
-hostIP
- |
-Host IP address
- |
-
-nameSpace
- |
-Cluster namespace
- |
-
-netDevice
- |
-NIC name
- |
-
-nodeIP
- |
-Host IP address
- |
-
-nodeName
- |
-Host name
- |
-
-
-
-
-
Disk Metrics and Dimensions
-
-
Table 1 Disk metricsMetric
- |
-Description
- |
-Value Range
- |
-Unit
- |
-
|---|
-
-Disk read rate (diskReadRate)
- |
-Volume of data read from a disk per second
- |
-≥ 0
- |
-KB/s
- |
-
-Disk write rate (diskWriteRate)
- |
-Volume of data written into a disk per second
- |
-≥ 0
- |
-KB/s
- |
-
-
-
-
-
-
Table 2 Dimensions of disk metricsDimension
- |
-Description
- |
-
|---|
-
-clusterId
- |
-Cluster ID
- |
-
-diskDevice
- |
-Disk name
- |
-
-hostID
- |
-Host ID
- |
-
-nameSpace
- |
-Cluster namespace
- |
-
-nodeIP
- |
-Host IP address
- |
-
-nodeName
- |
-Host name
- |
-
-
-
-
-
File System Metrics and Dimensions
-
-
Table 1 File system metricsMetric
- |
-Description
- |
-Value Range
- |
-Unit
- |
-
|---|
-
-Available disk space (diskAvailableCapacity)
- |
-Disk space that has not been used
- |
-≥ 0
- |
-MB
- |
-
-Total disk space (diskCapacity)
- |
-Total disk space
- |
-≥ 0
- |
-MB
- |
-
-Disk read/write status (diskRWStatus)
- |
-Read/write status of a disk
- |
-0 or 1
-- 0: read/write
- 1: read-only
- |
-None
- |
-
-Disk usage (diskUsedRate)
- |
-Percentage of the used disk space to the total disk space
- |
-≥ 0
- |
-%
- |
-
-
-
-
-
-
Table 2 Dimensions of file system metricsDimension
- |
-Description
- |
-
|---|
-
-clusterId
- |
-Cluster ID
- |
-
-clusterName
- |
-Cluster name
- |
-
-fileSystem
- |
-File system
- |
-
-hostID
- |
-Host ID
- |
-
-mountPoint
- |
-Mount point
- |
-
-nameSpace
- |
-Cluster namespace
- |
-
-nodeIP
- |
-Host IP address
- |
-
-nodeName
- |
-Host name
- |
-
-
-
-
-
Host Metrics and Dimensions
-
-
Table 1 Host metricsMetric
- |
-Description
- |
-Value Range
- |
-Unit
- |
-
|---|
-
-Total CPU cores (cpuCoreLimit)
- |
-Total number of CPU cores that have been applied for a measured object
- |
-≥ 1
- |
-Cores
- |
-
-Used CPU cores (cpuCoreUsed)
- |
-Number of CPU cores used by a measured object
- |
-≥ 0
- |
-Cores
- |
-
-CPU usage (cpuUsage)
- |
-CPU usage of a measured object
- |
-0%–100%
- |
-%
- |
-
-Available disk space (diskAvailableCapacity)
- |
-Disk space that has not been used
- |
-≥ 0
- |
-MB
- |
-
-Total disk space (diskCapacity)
- |
-Total disk space
- |
-≥ 0
- |
-MB
- |
-
-Disk read rate (diskReadRate)
- |
-Volume of data read from a disk per second
- |
-≥ 0
- |
-KB/s
- |
-
-Disk read/write status (diskRWStatus)
- |
-Read/write status of a disk
- |
-0 or 1
-- 0: read/write
- 1: read-only
- |
-None
- |
-
-Disk usage (diskUsedRate)
- |
-Percentage of the used disk space to the total disk space
- |
-≥ 0
- |
-%
- |
-
-Disk write rate (diskWriteRate)
- |
-Volume of data written into a disk per second
- |
-≥ 0
- |
-KB/s
- |
-
-Available physical memory (freeMem)
- |
-Available physical memory of a measured object
- |
-≥ 0
- |
-MB
- |
-
-Available virtual memory (freeVirMem)
- |
-Available virtual memory of a measured object
- |
-≥ 0
- |
-MB
- |
-
-Physical memory usage (memUsedRate)
- |
-Percentage of the used physical memory to the total physical memory
- |
-0%–100%
- |
-%
- |
-
-Host status (nodeStatus)
- |
-Host status
- |
-- 0: Normal
- Other values: Abnormal
- |
-None
- |
-
-NTP offset (ntpOffset)
- |
-Offset between the local time of the host and the NTP server time. When the NTP offset is closer to 0, the local time of the host is closer to the time of the NTP server.
- |
-None
- |
-ms
- |
-
-NTP server status (ntpServerStatus)
- |
-Whether the host is connected to the NTP server
- |
-0 or 1
-- 0: Connected
- 1: Unconnected
- |
-None
- |
-
-NTP sync status (ntpStatus)
- |
-Whether the local time of the host is synchronous with the NTP server time
- |
-0 or 1
-- 0: Synchronous
- 1: Asynchronous
- |
-None
- |
-
-Processes (processNum)
- |
-Number of processes on a measured object
- |
-≥ 0
- |
-None
- |
-
-Downlink rate (recvBytesRate)
- |
-Inbound network traffic rate of a measured object
- |
-≥ 0
- |
-Byte per Second (BPS)
- |
-
-Downlink rate (recvPackRate)
- |
-Number of data packets received by the NIC per second
- |
-≥ 0
- |
-Packet per Second (PPS)
- |
-
-Downlink error rate (recvErrPackRate)
- |
-Number of error packets received by the NIC per second
- |
-≥ 0
- |
-PPS
- |
-
-Uplink rate (sendBytesRate)
- |
-Outbound network traffic rate of a measured object
- |
-≥ 0
- |
-BPS
- |
-
-Uplink error rate (sendErrPackRate)
- |
-Number of error packets sent by the NIC per second
- |
-≥ 0
- |
-PPS
- |
-
-Uplink rate (sendPackRate)
- |
-Number of data packets sent by the NIC per second
- |
-≥ 0
- |
-PPS
- |
-
-Total rate (totalBytesRate)
- |
-Total inbound and outbound network traffic rate of a measured object
- |
-≥ 0
- |
-BPS
- |
-
-Total physical memory (totalMem)
- |
-Total physical memory that has been applied for a measured object
- |
-≥ 0
- |
-MB
- |
-
-Total virtual memory (totalVirMem)
- |
-Total virtual memory of a measured object
- |
-≥ 0
- |
-MB
- |
-
-Virtual memory usage (virMemUsedRate)
- |
-Percentage of the used virtual memory to the total virtual memory
- |
-0%–100%
- |
-%
- |
-
-GPU usage (gpuUtil)
- |
-GPU usage of a measured object
- |
-0%–100%
- |
-%
- |
-
-
-
-
-
-
Table 2 Dimensions of host metricsDimension
- |
-Description
- |
-
|---|
-
-clusterId
- |
-Cluster ID
- |
-
-clusterName
- |
-Cluster name
- |
-
-gpuName
- |
-GPU name
- |
-
-gpuID
- |
-GPU ID
- |
-
-hostID
- |
-Host ID
- |
-
-nameSpace
- |
-Cluster namespace
- |
-
-nodeIP
- |
-Host IP address
- |
-
-nodeName
- |
-Host name
- |
-
-
-
-
-
Cluster Metrics and Dimensions
-
-
Table 1 Cluster metricsMetric
- |
-Description
- |
-Value Range
- |
-Unit
- |
-
|---|
-
-Total CPU cores (cpuCoreLimit)
- |
-Total number of CPU cores that have been applied for a measured object
- |
-≥ 1
- |
-Cores
- |
-
-Used CPU cores (cpuCoreUsed)
- |
-Number of CPU cores used by a measured object
- |
-≥ 0
- |
-Cores
- |
-
-CPU usage (cpuUsage)
- |
-CPU usage of a measured object
- |
-0%–100%
- |
-%
- |
-
-Available disk space (diskAvailableCapacity)
- |
-Disk space that has not been used
- |
-≥ 0
- |
-MB
- |
-
-Total disk space (diskCapacity)
- |
-Total disk space
- |
-≥ 0
- |
-MB
- |
-
-Disk usage (diskUsedRate)
- |
-Percentage of the used disk space to the total disk space
- |
-≥ 0
- |
-%
- |
-
-Available physical memory (freeMem)
- |
-Available physical memory of a measured object
- |
-≥ 0
- |
-MB
- |
-
-Available virtual memory (freeVirMem)
- |
-Available virtual memory of a measured object
- |
-≥ 0
- |
-MB
- |
-
-Physical memory usage (memUsedRate)
- |
-Percentage of the used physical memory to the total physical memory
- |
-0%–100%
- |
-%
- |
-
-Downlink rate (recvBytesRate)
- |
-Inbound network traffic rate of a measured object
- |
-≥ 0
- |
-Byte per Second (BPS)
- |
-
-Uplink rate (sendBytesRate)
- |
-Outbound network traffic rate of a measured object
- |
-≥ 0
- |
-BPS
- |
-
-Total physical memory (totalMem)
- |
-Total physical memory that has been applied for a measured object
- |
-≥ 0
- |
-MB
- |
-
-Total virtual memory (totalVirMem)
- |
-Total virtual memory of a measured object
- |
-≥ 0
- |
-MB
- |
-
-Virtual memory usage (virMemUsedRate)
- |
-Percentage of the used virtual memory to the total virtual memory
- |
-0%–100%
- |
-%
- |
-
-GPU usage (gpuUtil)
- |
-GPU usage of a measured object
- |
-0%–100%
- |
-%
- |
-
-
-
-
-
-
Table 2 Dimensions of cluster metricsDimension
- |
-Description
- |
-
|---|
-
-clusterId
- |
-Cluster ID
- |
-
-clusterName
- |
-Cluster name
- |
-
-projectId
- |
-Project ID
- |
-
-
-
-
-
Container Metrics and Dimensions
-
-
Table 1 Container metricsMetric
- |
-Description
- |
-Value Range
- |
-Unit
- |
-
|---|
-
-Total CPU cores (cpuCoreLimit)
- |
-Total number of CPU cores that have been applied for a measured object
- |
-≥ 1
- |
-Cores
- |
-
-Used CPU cores (cpuCoreUsed)
- |
-Number of CPU cores used by a measured object
- |
-≥ 0
- |
-Cores
- |
-
-CPU usage (cpuUsage)
- |
-Percentage of the used CPU cores to the total CPU cores
- |
-0%–100%
- |
-%
- |
-
-Disk read rate (diskReadRate)
- |
-Volume of data read from a disk per second
- |
-≥ 0
- |
-KB/s
- |
-
-Disk write rate (diskWriteRate)
- |
-Volume of data written into a disk per second
- |
-≥ 0
- |
-KB/s
- |
-
-Available file system (filesystemAvailable)
- |
-Available file system capacity of a measured object
- |
-≥ 0
- |
-MB
- |
-
-Total file system (filesystemCapacity)
- |
-Total file system capacity of a measured object
- |
-≥ 0
- |
-MB
- |
-
-File system usage (filesystemUsage)
- |
-File system usage of a measured object Percentage of the used file system to the total file system This metric is supported only for the containers using the device mapper in the Kubernetes cluster of version 1.11 or later.
- |
-0%–100%
- |
-%
- |
-
-Total physical memory (memCapacity)
- |
-Total physical memory that has been applied for a measured object
- |
-≥ 0
- |
-MB
- |
-
-Physical memory usage (memUsage)
- |
-Percentage of the used physical memory to the total physical memory
- |
-0%–100%
- |
-%
- |
-
-Used physical memory (memUsed)
- |
-Used physical memory of a measured object
- |
-≥ 0
- |
-MB
- |
-
-Downlink rate (recvBytesRate)
- |
-Inbound network traffic rate of a measured object
- |
-≥ 0
- |
-Byte per Second (BPS)
- |
-
-Downlink rate (recvPackRate)
- |
-Number of data packets received by the NIC per second
- |
-≥ 0
- |
-Packet per Second (PPS)
- |
-
-Downlink error rate (recvErrPackRate)
- |
-Number of error packets received by the NIC per second
- |
-≥ 0
- |
-PPS
- |
-
-Error packets (rxPackErrors)
- |
-Number of error packets received by a measured object
- |
-≥ 0
- |
-Packets
- |
-
-Uplink rate (sendBytesRate)
- |
-Outbound network traffic rate of a measured object
- |
-≥ 0
- |
-BPS
- |
-
-Uplink error rate (sendErrPackRate)
- |
-Number of error packets sent by the NIC per second
- |
-≥ 0
- |
-PPS
- |
-
-Uplink rate (sendPackRate)
- |
-Number of data packets sent by the NIC per second
- |
-≥ 0
- |
-PPS
- |
-
-Status (status)
- |
-Docker container status
- |
-0 or 1
-
- |
-None
- |
-
-GPU usage (gpuUtil)
- |
-GPU usage of a measured object
- |
-0%–100%
- |
-%
- |
-
-
-
-
-
-
Table 2 Dimensions of container metricsDimension
- |
-Description
- |
-
|---|
-
-appID
- |
-Service ID
- |
-
-appName
- |
-Service name
- |
-
-clusterId
- |
-Cluster ID
- |
-
-clusterName
- |
-Cluster name
- |
-
-containerID
- |
-Container ID
- |
-
-containerName
- |
-Container name
- |
-
-deploymentName
- |
-Kubernetes deployment name
- |
-
-kind
- |
-Application type
- |
-
-nameSpace
- |
-Cluster namespace
- |
-
-podID
- |
-Pod ID
- |
-
-podName
- |
-Pod name
- |
-
-serviceID
- |
-Inventory ID
- |
-
-
-
-
-
Process Metrics and Dimensions
-
-
Table 1 Process metricsMetric
- |
-Description
- |
-Value Range
- |
-Unit
- |
-
|---|
-
-Total CPU cores (cpuCoreLimit)
- |
-Total number of CPU cores that have been applied for a measured object
- |
-≥ 1
- |
-Cores
- |
-
-Used CPU cores (cpuCoreUsed)
- |
-Number of CPU cores used by a measured object
- |
-≥ 0
- |
-Cores
- |
-
-CPU usage (cpuUsage)
- |
-Percentage of the used CPU cores to the total CPU cores
- |
-0%–100%
- |
-%
- |
-
-Handles (handleCount)
- |
-Number of handles used by a measured object
- |
-≥ 0
- |
-None
- |
-
-Total physical memory (memCapacity)
- |
-Total physical memory that has been applied for a measured object
- |
-≥ 0
- |
-MB
- |
-
-Physical memory usage (memUsage)
- |
-Percentage of the used physical memory to the total physical memory
- |
-0%–100%
- |
-%
- |
-
-Used physical memory (memUsed)
- |
-Used physical memory of a measured object
- |
-≥ 0
- |
-MB
- |
-
-Status (status)
- |
-Process status
- |
-0 or 1
-
- |
-None
- |
-
-Threads (threadsCount)
- |
-Number of threads used by a measured object
- |
-≥ 0
- |
-None
- |
-
-Total virtual memory (virMemCapacity)
- |
-Total virtual memory that has been applied for a measured object
- |
-≥ 0
- |
-MB
- |
-
-
-
-
-
-
Table 2 Dimensions of process metricsDimension
- |
-Description
- |
-
|---|
-
-appName
- |
-Service name
- |
-
-clusterId
- |
-Cluster ID
- |
-
-clusterName
- |
-Cluster name
- |
-
-nameSpace
- |
-Cluster namespace
- |
-
-processID
- |
-Process ID
- |
-
-processName
- |
-Process name
- |
-
-serviceID
- |
-Inventory ID
- |
-
-
-
-
-
Instance Metrics and Dimensions
-Instance metrics consist of container or process metrics. The dimensions of instance metrics are the same as those of container or process metrics. For details, see Container Metrics and Dimensions and Process Metrics and Dimensions.
-
For workloads deployed on Cloud Container Engine (CCE), AOM supports drill-down from services to service instances, containers, and processes. For services that directly run on VMs, AOM supports drill-down from services to service instances and processes. In this way, you can implement multi-dimensional monitoring.
-
Service Metrics and Dimensions
-Service metrics consist of instance metrics. The dimensions of service metrics are the same as those of instance metrics. For details, see Instance Metrics and Dimensions.
-
Monitoring Services
-Services refer to containers and common processes you deploy. For example, a workload on Cloud Container Engine (CCE) is a service, and the Tomcat running on a VM is also a service.
-
The service list displays the type, CPU usage, memory usage, and alarm status of each service, helping you learn services. You can click a service name to learn more information. AOM supports drill-down from a service to a service instance, a container, and then to a process. In this way, you can implement multi-dimensional monitoring.
-
Procedure
- In the navigation pane, choose Service Monitoring and perform the following operations as required:
- Adding an alias
If a service name is complex and difficult to identify, add an alias for the service.
-Choose More > Add alias in the Operation column, and specify an alias.
-
- - Adding a tag
Tags are used to identify services. You can distinguish system and non-system services using tags. By default, AOM adds the System Service tag to system services, including icagent, css-defender, nvidia-driver-installer, nvidia-gpu-device-plugin, kube-dns, org.tanukisoftware.wrapper.WrapperSimpleApp, evs-driver, obs-driver, sfs-driver, icwatchdog, and sh. You can click 
in the upper right corner to select or deselect Hide system services. You can also customize tags to facilitate service management.
-In the service list, choose More > Modify Tag in the Operation column of the service. On the displayed page, click 
to enter a tag, and click 
and OK. After the tag is added, enter a tag keyword in the search box in the upper right corner of the page to search for services.
- - By default, the Tag column of the service list is hidden. You can click
in the upper right corner and select or deselect Tag to show or hide them. In the Tags column, use double quotation marks ("") to separate tags. Enter the content in double quotation marks when using tags to search for services. - Rule Name
- Sys_Rule: AOM automatically discovers services based on the built-in Sys_Rule.
-- Default_Rule: AOM automatically discovers services based on the built-in Default_Rule.
-
-
-
- - Click
to switch to the card view or click 
to switch to the list. - Set filter criteria to search for the desired service.
You can select a cluster from the drop-down list above the service list to filter services, or directly enter a service name in the search box to search for a service.
- - Click the service name. The service details page is displayed.
- On the Resource List tab page, view the service details.
- On the Instance List tab page, view the instance details.
- On the Host List tab page, view the host details.
- On the Alarm Analysis tab page, view the alarm details.
- - Click an instance name to monitor related resource usage and health status.
- Click a host name to view details about the host where the service is deployed.
-
-
-- Click the View Monitor Graphs tab to monitor the various metrics of the service.
-
-
-
Creating Threshold Rules
-To use threshold rules, customize threshold conditions first. If a metric value meets a threshold condition, AOM generates a threshold alarm. If no metric data is reported, AOM generates an insufficient data event.
-
AOM is interconnected with Simple Message Notification (SMN). After you set a notification policy on the SMN console, notifications are sent by email or Short Message Service (SMS) message if the threshold rule status (Exceeded, OK, or Insufficient) changes. In this way, you can identify and handle exceptions at the earliest time.
-
Precautions
- You can create a maximum of 1000 threshold rules. To create more rules when the maximum number is reached, delete unnecessary rules.
- Setting a notification policy
To send notifications by email or SMS message if the threshold rule status (
Exceeded,
OK, or
Insufficient) changes, set a notification policy on the SMN console according to the following procedure. If you do not need to receive notifications by email or SMS message, skip the following operations. Procedure:
- Create a topic by referring to Creating a Topic.
- Set a topic policy by referring to Configuring Topic Policies.
Select apm for Services that can publish messages to this topic. Otherwise, notifications cannot be sent.
- - Add a subscriber (email or SMS message recipient) for the topic by referring to Adding a Subscription.
-
-
-
Creating Threshold Rules
- Log in to the management console.
- Under Application, click Application Operations Management.
- In the navigation pane, choose Alarm Center > Threshold Rules. Then, click Add Threshold Rule in the upper right corner.
- Create a threshold rule.
- Select resources: Enter a threshold rule name, select a resource type, select the resources to be monitored from the resource tree, and click Next.
- You can select a maximum of 10 resources from the resource tree.
- When multiple resources are selected, multiple threshold rules will be created after the creation is complete. Each resource is monitored by a threshold rule. A rule name consists of the threshold rule name you enter in the Threshold Name text box, and a sequence number ranging from 0 to 99. The earlier a resource is selected, the smaller its sequence number.
For example, enter Monitor_Host_cpuUsage in the Threshold Name text box and select the aom-1 host and then the aom-2 host from the resource tree. In this way, threshold rules Monitor_Host_cpuUsage0 and Monitor_Host_cpuUsage1 will be generated. The former monitors the aom-1 host while the latter monitors the aom-2 host.
-
-
-Figure 1 Selecting resources
- - Customize a threshold. Specifically, select the metric to be monitored, and set parameters such as Threshold Condition, Consecutive Period (s), Alarm Severity, Statistic, and Send Notification.
- Threshold Condition: Trigger condition of a threshold alarm. A threshold condition consists of two parts: determination condition (≥, ≤, >, or <) and threshold value. For example, if Threshold Condition is set to > 85 and an actual metric value exceeds 85, a threshold alarm will be generated.
- Consecutive Period (s): If a metric value meets the threshold condition for a specified number of consecutive periods, a threshold alarm will be generated.
- Statistic: Method used to measure metrics.
- Statistical Period: Interval at which metric data is collected. The system collects a data point every minute to determine the status of the threshold rule.
- Send Notification: Whether to send a notification by email or SMS message if the threshold rule status (Exceeded, OK, or Insufficient) changes.
- If you need to receive notifications by email or SMS message, select Yes, set a notification policy, select the created topic, and select a trigger condition.
- If you do not need to receive notifications by email or SMS message, select No.
- - Trigger Condition: Condition for sending notifications.
You can select multiple trigger conditions for a threshold rule. For example, to receive notifications if the threshold status changes to Exceeded, select Threshold crossing. To receive notifications upon any threshold status change, select all trigger conditions.
-
-
-Figure 2 Customizing a threshold
-
- - Click Submit. As shown in the following figure, multiple threshold rules are created. Each resource is monitored by an independent rule.
If the CPU usage of a host exceeds 85%, a threshold alarm is generated on the alarm page. You can choose Alarm Center > Alarms in the navigation pane to view the alarm. If the host meets the preset notification policy, an email or SMS message will be sent to the specified recipient.
-Figure 3 Threshold rules
-
-
-
Related Operations
After creating a threshold rule, you can also perform the operations described in Table 1.
-
-
Table 1 Related operationsOperation
- |
-Description
- |
-
|---|
-
-Modify a threshold rule
- |
-Click Modify in the Operation column.
- |
-
-Delete a threshold rule
- |
-- To delete a threshold rule, click Delete in the Operation column.
- To delete one or more threshold rules, select them and click Delete above the threshold rule list.
- |
-
-Search for a threshold rule
- |
-Enter a keyword of the threshold rule name in the search box in the upper right corner and click  .
- |
-
-View a threshold rule
- |
-Click  next to a threshold rule to view its details.
- |
-
-View an alarm
- |
-If the metric value of a resource meets a threshold condition in the specified number of consecutive periods, a threshold alarm will be sent.
-In the navigation pane, choose Alarm Center > Alarms to view the alarm.
- |
-
-View an event
- |
-During the configured consecutive periods, if no metric data of a resource is reported, an insufficient data event will be sent.
-In the navigation pane, choose Alarm Center > Events to view the event.
- |
-
-
-
-
-
-
Overview
-The Overview page provides full-link, multi-layer, and one-stop O&M for applications and resources. The following types of graphs are supported: infrastructure monitoring, host monitoring (CPU and memory), service monitoring (CPU and memory), instance monitoring (CPU and memory), host monitoring (disk), host monitoring (network), cluster monitoring (CPU and memory), and cluster monitoring (disk).
-
- Log in to the management console.
- Under Application, click Application Operations Management.
- In the navigation pane, choose Overview to view information.
-
Infrastructure Monitoring
Figure 1 Infrastructure monitoring
-
This area displays infrastructure metrics. You can select one or all clusters to view monitoring information. In the preceding figure, all clusters are selected. The information includes:
-
- Host running status, CPU usage, and physical memory usage.
- Trend graph of network traffic in the last hour. The values of each point in the graph respectively indicate the total downlink/uplink rates of all clusters in one minute. The values displayed above the trend graph respectively indicate the total downlink/uplink rates of all clusters at the latest time point.
- Trend graph of CPU usage and memory usage in the last hour. The values of each point in the graph respectively indicate the average CPU and memory usage of all clusters in one minute. The values displayed above the trend graph respectively indicate the average CPU and memory usage of all clusters at the latest time point.
-
-
Host Monitoring (CPU and Memory)
Figure 2 Host monitoring (CPU and memory)
-
The information includes:
-
- The top 5 hosts with high CPU and memory usage in the last minute.
- Trend graph of the CPU and memory usage of the selected host in the last hour. The values of each point in the graph respectively indicate the CPU and memory usage of the host in one minute.
- CPU and memory usage of the selected host at the latest time point, which is displayed above the trend graph.
-
When the value of a metric exceeds a threshold, a red line is displayed in the trend graph, alerting you that such a value needs attention.
-
-
-
Service Monitoring (CPU and Memory)
Figure 3 Service monitoring (CPU and memory)
-
The information includes:
-
- The top 5 services with high CPU and memory usage in the last minute.
- Trend graph of the CPU and memory usage of the selected service in the last hour. The values of each point in the graph respectively indicate the CPU and memory usage of the service in one minute.
- CPU and memory usage of the selected service at the latest time point, which is displayed above the trend graph.
- Option
, which can be selected to hide system services.
-
-
Instance Monitoring (CPU and Memory)
Figure 4 Instance monitoring (CPU and memory)
-
The information includes:
-
- The top 5 instances with high CPU and memory usage in the last minute.
- Trend graph of the CPU and memory usage of the selected instance in the last hour. The values of each point in the graph respectively indicate the CPU and memory usage of the instance in one minute.
- CPU and memory usage of the selected instance at the latest time point, which is displayed above the trend graph.
- Option
, which can be selected to hide system instances.
-
-
Host Monitoring (Disk)
Figure 5 Host monitoring (disk)
-
The information includes:
-
- The top 5 hosts with high disk read/write rate in the last minute.
- Trend graph of the disk read/write rate of the selected host in the last hour. The values of each point in the graph respectively indicate the disk read/write rate of the selected host in one minute.
- Disk read/write rate of the selected host at the latest time point, which is displayed above the trend graph.
-
-
Host Monitoring (Network)
Figure 6 Host monitoring (network)
-
The information includes:
-
- The top 5 hosts with high uplink/downlink network rate in the last minute.
- Trend graph of the uplink/downlink network rate of the selected host in the last hour. The values of each point in the graph respectively indicate the uplink/downlink network rate of the selected host in one minute.
- Uplink/downlink network rate of the selected host at the latest time point, which is displayed above the trend graph.
-
-
Cluster Monitoring (CPU and Memory)
Figure 7 Cluster monitoring (CPU and memory)
-
The information includes:
-
- The top 5 clusters with high CPU and memory usage in the last minute.
- Trend graph of the CPU and memory usage of the selected cluster in the last hour. The values of each point in the graph respectively indicate the CPU and memory usage of the cluster in one minute.
- CPU and memory usage of the selected cluster at the latest time point, which is displayed above the trend graph.
-
- When the value of a metric exceeds a threshold, a red line is displayed in the trend graph, alerting you that such a value needs attention.
- When the values of multiple metrics exceed thresholds, multiple red lines are displayed in the trend graph. You can hover over the trend graph to view the values of different metrics, as shown in the following figure.
-
-
-
-
Cluster Monitoring (Disk)
Figure 8 Cluster monitoring (disk)
-
The information includes:
-
- The top 5 clusters with high disk usage in the last minute.
- Trend graph of the disk usage of the selected cluster in the last hour. The value of each point in the graph indicates the disk usage of the cluster in one minute.
- Disk usage of the selected cluster at the latest time point, which is displayed above the trend graph.
-
-
Related Operations
You can also perform the operations described in Table 1.
-
-
Table 1 Related operationsOperation
- |
-Description
- |
-
|---|
-
-Favorites
- |
-Click Add to Favorites in the upper right corner of each monitoring area to move a graph to the Favorites.
-Click  on the right of the page to move a graph from the Favorites to the monitoring area.
- |
-
-Enlarging a metric graph
- |
-Click  in the upper right corner of a metric graph to zoom it in.
- |
-
-Drilling down blue texts
- |
-Click blue texts, for example, a host name, to drill down to the details page, as shown in the following figure.
-
- |
-
-
-
-
-
-
Obtaining an AK/SK
- Each user can create a maximum of two AK/SK pairs. Once they are generated, they are permanently valid.
-
-
- AK: unique ID associated with the SK. It is used together with the SK to sign requests.
- SK: secret access key used in conjunction with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.
-
Procedure
- Log in to the management console, hover the mouse pointer over the username in the upper right corner, and select My Credentials from the drop-down list.
- On the My Credentials page, click the Access Keys tab.
- Click Create Access Key. In the dialog box that is displayed, enter the login password and verification code sent to your email or mobile phone.
- Click OK and download the generated AK/SK pair.
-
-
-
Monitoring Metrics
-AOM displays metric data of each resource on the Metric Monitoring page. You can monitor metric values and trends in real time, add metrics to dashboards, create threshold rules, and export reports for real-time monitoring and correlation analysis.
-
Procedure
- Log in to the management console.
- Under Application, click Application Operations Management.
- In the navigation pane, choose View Management > Metric Monitoring.
- Select up to 10 metrics from the metric tree on the left to monitor. For details, see Metric Description.
- Set metric parameters according to Table 1, view the metric graphs on the right, and analyze metric data from multiple dimensions.
-
Table 1 Metric parametersParameter
- |
-Description
- |
-
|---|
-
-Time Range
- |
-Time period when metrics are monitored.
- |
-
-Statistical Period
- |
-Interval at which metric data is collected.
- |
-
-Statistic
- |
-Method used to measure metrics.
- NOTE: - The number of samples equals to the count of data points.
- If you change the statistical method, the new setting will take effect for all metrics.
-
- |
-
-
-
-
-
-
Related Operations
You can also perform the operations described in Table 2.
-
-
Table 2 Related operationsOperation
- |
-Description
- |
-
|---|
-
-Add a metric graph to a dashboard
- |
-Click Add to Dashboard to add a metric graph to a dashboard.
- |
-
-Add a threshold rule for a metric
- |
-Click Add to Threshold Rule, set threshold rule parameters, and click Submit to add a threshold rule.
- |
-
-Export a monitoring report
- |
-Click Export Report to export a metric graph as a CSV file to a local PC.
- |
-
-Set an interpolation mode
- |
-By default, AOM uses Null to represent breakpoints in a metric graph, as shown in Figure 1. However, a metric graph with breakpoints is not suitable for reports or presentation. To solve the problem, set the value of Interpolation Mode to 0 or Average to interpolate values. In this way, you can replace the missing metric data and avoid breakpoints.
-The value of Interpolation Mode can be Null, 0, or Average.
-- Null: Breakpoints are represented by Null by default.
Figure 1 Graph when the value of Interpolation Mode is Null
- - 0: Breakpoints are represented by 0.
Figure 2 Graph when the value of Interpolation Mode is 0
- - Average: Breakpoints are represented by the average value.
Figure 3 Graph when the value of Interpolation Mode is Average
- NOTE: If the value of Interpolation Mode is set to Average, breakpoints will be represented by average values. The following describes how to calculate average values.
- A metric graph may have multiple breakpoints. When multiple breakpoints exist, values will be interpolated for these breakpoints from left to right. The following uses the first breakpoint in a graph as an example to describe the method of calculating the average value. This method can also be applied to other breakpoints.
- - If the first breakpoint is at the start of a metric graph, the value of the breakpoint is the first valid data from its next point to the right.
For example, if a metric graph has points a, b, c, d, and e, where a = Null, b = Null, c = Null, d = Null, and e = 5, the value of the first breakpoint (that is, point a) is 5.
- - If the first breakpoint is in the middle of a metric graph, there are the following two scenarios:
Scenario 1: If the values of the previous and next points of the breakpoint are valid, the value of the breakpoint is the average value of these two points.
-For example, if a metric graph has points a, b, c, d, and e, where a = 1, b = Null, c = 3, d = Null, and e = 5, the value of the first breakpoint (that is, point b) is (a + c)/2 = (1 + 3)/2 = 2.
-Scenario 2: If the value of the previous point of the breakpoint is valid and the value of its next point is null, the value of the breakpoint is the average value of its previous point and the first valid data from its next point to the right.
-For example, if a metric graph has points a, b, c, d, and e, where a = 1, b = Null, c = Null, d = Null, and e = 5, the value of the first breakpoint (that is, point b) is (a + e)/2= (1 + 5)/2 = 3. Because values are interpolated for breakpoints from left to right, the value of the second breakpoint (that is, point c) is (b + e)/2 = (3 + 5)/2 = 4, the value of the third breakpoint (that is, point d) is (c + e)/2 = (4 + 5)/2 = 4.5.
- - If the first breakpoint is at the end of a metric graph, the value of the breakpoint is the value of the previous point.
For example, if a metric graph has points a, b, c, d, and e, where a = 1, b = 2, c = 3, d = 4, and e = Null, the value of the first breakpoint (that is, point e) is 4.
- - If all points in a metric graph are breakpoints, the values of all these points are still Null, even though you set the value of Interpolation Mode to Average.
For example, if a metric graph has points a, b, c, d, and e, where a = Null, b = Null, c = Null, d = Null, and e = Null, the values of all breakpoints are Null.
-
-
-
- |
-
-
-
-
-
-
Monitoring Workloads
-AOM enables you to monitor workloads deployed on Cloud Container Engine (CCE).
-
Precautions
The workload status can be Normal, Abnormal, Warning, Silent, or Deleted. If a workload generates a threshold alarm or is abnormal due to a network exception, host power-off, or shutdown, the workload status becomes Abnormal. For more information, see What Can I Do If Resources Are Not Running Properly?.
-
-
Procedure
- Log in to the management console.
- Under Application, click Application Operations Management.
- In the navigation pane, choose Workload Monitoring.
The workload list displays the status, CPU usage, and memory usage of each workload, helping you learn the running status of each workload.
- - Set filter criteria to search for a desired workload.
- Click the workload to enter its details page. AOM supports drill-down from a workload to an instance, and then to a container. By viewing the status of each layer, you can monitor the workload in a multi-dimensional manner.
- On the Resource List page, view instance status, CPU usage, and physical memory usage, as shown in the following figure.
Click an instance to monitor information such as resource usage and health status.
-
-
-- Click the View Monitor Graphs tab to view the metrics of the workload, such as the CPU usage and memory usage, as shown in the following figure.
-- Creating a view template
AOM provides a default view template (Service Template) that can be modified. You can also click the plus sign (+) in 
to customize view templates.
- - Adding a metric graph
You can click 
to add a line graph or 
to add a digit graph to the view template. You can also delete, move, and copy metric graphs in the view template according to Dashboard.
- - Adding a view template to a dashboard
On the workload details page, choose More > Add To Dashboard in the upper right corner to add the view template to a dashboard for monitoring.
-
-
-
-
-
ICAgent Management
-
-
-
diff --git a/docs/aom/umn/aom_02_2012.html b/docs/aom/umn/aom_02_2012.html
deleted file mode 100644
index 382eddae..00000000
--- a/docs/aom/umn/aom_02_2012.html
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-Installing the ICAgent
-ICAgent is the collector of AOM. It runs on each host to collect metrics and logs in real time. Before using AOM, install the ICAgent. Otherwise, AOM cannot be used.
-
VM Mode
Prerequisite
-
- Before installing the ICAgent, ensure that the time and time zone of the local browser are consistent with those of the server. Otherwise, metric data of services and servers displayed on the console may be inaccurate.
- You have obtained an AK/SK. For details, see Obtaining an AK/SK.
-
Procedure
-
-
- Log in to the management console.
- Under Application, click Application Operations Management.
- In the navigation pane, choose Agent Management.
- Select Other: user-defined nodes, and click Install ICAgent.
- Generate and copy the ICAgent installation command.
- Use a remote login tool, such as PuTTY, to log in as the root user to the server where the ICAgent is to be installed, run the command copied in 5, and enter the obtained AK/SK as prompted to install the ICAgent.
- If the message ICAgent install success. is displayed, the ICAgent is successfully installed in the /opt/oss/servicemgr/ directory. After the ICAgent is successfully installed, choose Agent Management in the navigation pane on the left, and select Other: user-defined nodes to view the ICAgent status of the server.
- If the ICAgent fails to be installed, uninstall it according to Uninstalling the ICAgent and then install it again. If the problem persists, contact technical support.
-
-
-
Container Mode
After a cluster is created on the Cloud Container Engine (CCE) console, the system automatically installs the ICAgent on all hosts in the cluster. After the ICAgent is uninstalled, install it again according to the following procedure:
-
- Log in to the management console.
- Under Application, click Application Operations Management.
- In the navigation pane, choose Agent Management.
- Install the ICAgent. The ICAgent is installed in batches by cluster. That is, the ICAgent is installed on all hosts in a cluster at a time.
- Select Cluster: xxx (xxx indicates the name of the cluster created on the CCE console) from the drop-down list on the right of the page.
- Click Install ICAgent. In the displayed dialog box, click Yes.
-The ICAgent begins to be installed. Please wait. When the ICAgent status changes from Installing to Running, the ICAgent is successfully installed.
-
-
-
Upgrading the ICAgent
-To ensure better collection experience, AOM will continuously upgrade ICAgent versions. When the system displays a message indicating that a new ICAgent version is available, perform the following operations:
-
- Log in to the management console.
- Under Application, click Application Operations Management.
- In the navigation pane, choose Agent Management.
- Upgrade the ICAgent. ICAgents are upgraded in batches by cluster. That is, ICAgents on all hosts in a cluster are upgraded at a time. For hosts where ICAgents have already been uninstalled, ICAgents are installed on them again.
- Select Cluster: xxx (xxx indicates the name of the cluster created on the CCE console) from the drop-down list on the right of the page.
- Click Upgrade ICAgent. In the displayed dialog box, click Yes.
-The ICAgent begins to be upgraded. Please wait. When the ICAgent status changes from Upgrading to Running, the ICAgent is successfully upgraded.
-
-
Uninstalling the ICAgent
-After the ICAgent is uninstalled from a host, metric and log data is unavailable. Exercise caution when performing this operation.
-
- Log in to the management console.
- Under Application, click Application Operations Management.
- In the navigation pane, choose Agent Management.
- Uninstall the ICAgent. The ICAgent is uninstalled in batches by cluster. That is, the ICAgent is uninstalled from all the hosts in a cluster at a time.
- Select Cluster: xxx (xxx indicates the name of the cluster created on the CCE console) from the drop-down list on the right of the page.
- Click Uninstall ICAgent. In the displayed dialog box, click Yes.
-The ICAgent begins to be uninstalled. Please wait. When the ICAgent status changes from Uninstalling to Uninstalled, the ICAgent is successfully uninstalled.
-
-
What Are the Usage Restrictions of AOM?
+OS Usage Restrictions
AOM supports multiple operating systems (OSs). When creating a host, ensure that its OS meets the requirements in Table 1. Otherwise, the host cannot be monitored by AOM.
+
+
Table 1 OSs and versions supported by AOMOS
+ |
+Version
+ |
+
|---|
+
+SUSE
+ |
+SUSE Enterprise 11 SP4 64-bit
+ |
+SUSE Enterprise 12 SP1 64-bit
+ |
+SUSE Enterprise 12 SP2 64-bit
+ |
+SUSE Enterprise 12 SP3 64-bit
+ |
+
+openSUSE
+ |
+13.2 64-bit
+ |
+42.2 64-bit
+ |
+15.0 64-bit (Currently, syslog logs cannot be collected.)
+ |
+
+EulerOS
+ |
+2.2 64-bit
+ |
+2.3 64-bit
+ |
+2.5 64-bit
+ |
+
+CentOS
+ |
+6.3 64-bit
+ |
+6.5 64-bit
+ |
+6.8 64-bit
+ |
+6.9 64-bit
+ |
+6.10 64-bit
+ |
+
+7.1 64-bit
+ |
+7.2 64-bit
+ |
+7.3 64-bit
+ |
+7.4 64-bit
+ |
+7.5 64-bit
+ |
+7.6 64-bit
+ |
+
+Ubuntu
+ |
+14.04 server 64-bit
+ |
+16.04 server 64-bit
+ |
+18.04 server 64-bit
+ |
+
+Fedora
+ |
+24 64-bit
+ |
+25 64-bit
+ |
+29 64-bit
+ |
+
+Debian
+ |
+7.5.0 32-bit
+ |
+7.5.0 64-bit
+ |
+8.2.0 64-bit
+ |
+8.8.0 64-bit
+ |
+9.0.0 64-bit
+ |
+
+
+
+
+
- For Linux x86_64 servers, AOM supports all the OSs and versions listed in the preceding table.
- For Linux Arm servers, AOM only supports CentOS 7.4 and later versions, and other OSs and versions listed in the preceding table.
+
+
+
Resource Usage Restrictions
When using AOM, learn about the restrictions in Table 2.
+
+
Table 2 Resource usage restrictionsCategory
+ |
+Object
+ |
+Usage Restrictions
+ |
+
|---|
+
+Dashboard
+ |
+Dashboard
+ |
+A maximum of 50 dashboards can be created in a region.
+ |
+
+Graph in a dashboard
+ |
+A maximum of 20 graphs can be added to a dashboard.
+ |
+
+Number of resources, threshold rules, components, or hosts in a graph
+ |
+- A maximum of 100 resources across clusters can be added to a line graph.
- Only one resource can be added to a digit graph.
- A maximum of 10 threshold rules can be added to a threshold status graph.
- A maximum of 10 hosts can be added to a host status graph.
- A maximum of 10 components can be added to a component status graph.
+ |
+
+Metric
+
+ |
+Metric data
+ |
+Metric data can be stored in the database for up to 30 days.
+ |
+
+Total number of metrics
+ |
+Up to 400,000 for a single account.
+Up to 100,000 for a small specification.
+
+ |
+
+Metric item
+ |
+After resources such as clusters, components, and hosts are deleted, their related metrics can be stored in the database for a maximum of 30 days.
+ |
+
+Dimension
+ |
+A maximum of 20 dimensions can be configured for a metric.
+ |
+
+Metric query API
+ |
+A maximum of 20 metrics can be queried at a time.
+ |
+
+Statistical period
+ |
+The maximum statistical period is 1 hour.
+ |
+
+Data points returned for a single query
+ |
+A maximum of 1440 data points can be returned each time.
+ |
+
+Custom metric
+ |
+Unlimited.
+ |
+
+Custom metric to be reported
+ |
+A single request cannot exceed 40 KB. The timestamp of a reported metric cannot 10 minutes later than the standard UTC time. In addition, out-of-order metrics are not received. That is, if a metric is reported at a certain time point, the metrics of earlier time points cannot be reported.
+ |
+
+Application metric
+ |
+- When the number of containers on a host exceeds 1000, the ICAgent stops collecting application metrics and sends the ICAgent Stopped Collecting Application Metrics alarm (ID: 34105).
- When the number of containers on a host is less than 1000, the ICAgent resumes the collection of application metrics and the ICAgent Stopped Collecting Application Metrics alarm is cleared.
+ |
+
+Resources consumed by the ICAgent
+ |
+When the ICAgent collects basic metrics, the resources consumed by the ICAgent are greatly affected by the number of containers and processes. On a VM without any services, the ICAgent consumes 30 MB memory and records 1% CPU usage. To ensure collection reliability, ensure that the number of containers running on a single node must be less than 1000.
+ |
+
+Log
+
+ |
+Size of a log
+ |
+The maximum size of each log is 10 KB. If a log exceeds 10 KB, the ICAgent does not collect it. That is, the log will be discarded.
+ |
+
+Log traffic
+ |
+A maximum of 10 MB/s is supported for each tenant in a region. If the log traffic exceeds 10 MB/s, logs may be lost.
+ |
+
+|
+ Log file
+ |
+Only text log files can be collected. Other types of log files, such as binary files, cannot be collected.
+ |
+
+The ICAgent can collect a maximum of 20 log files from a volume mounting directory.
+ |
+
+The ICAgent can collect a maximum of 1000 standard container output log files. These files must be in JSON format.
+ |
+
+Resources consumed during log file collection
+ |
+The resources consumed during log file collection are closely related to the log volume, number of files, network bandwidth, and backend service processing capability.
+ |
+
+Log loss
+ |
+ICAgent uses multiple mechanisms to ensure log collection reliability and prevent data loss. However, logs may be lost in the following scenarios:
+- The log rotation policy of Cloud Container Engine (CCE) is not used.
- Log files are rotated at a high speed, for example, once per second.
- Logs cannot be forwarded due to improper system security settings or syslog itself.
- The container running time, for example, shorter than 30s, is extremely short.
- A single node generates logs at a high speed, exceeding the allowed transmit bandwidth or log collection speed. Ensure that the log generation speed of a single node is lower than 5 MB/s.
+ |
+
+Log loss
+ |
+When a single log line exceeds 10,240 bytes, the line will be discarded.
+ |
+
+Log repetition
+ |
+When the ICAgent is restarted, identical data may be collected around the restart time.
+ |
+
+Alarm
+ |
+Alarm
+ |
+You can query the alarms generated in the last 15 days.
+ |
+
+Event
+ |
+You can query the events generated in the last 15 days.
+ |
+
+-
+ |
+Application discovery rule
+ |
+You can create a maximum of 100 application discovery rules.
+ |
+
+
+
+
+
+
Service Usage Restrictions
If the AMS-Access service is powered off or restarted unexpectedly when you use AOM, a metric data breakpoint occurs on some resources such as hosts, components, and containers in a collection period. This breakpoint is visible on the monitoring page and has no impacts. To avoid breakpoints in a metric graph, set the value of Interpolation Mode to 0 or average on the Metric Monitoring page. In this way, the system automatically replaces breakpoints with 0 or average values, as shown in Figure 1.
+
Figure 1 Changing the interpolation mode
+
+
How Do I Distinguish Alarms from Events?
+Similarities Between Alarms and Events
Both alarms and events are the information reported to AOM when the status of AOM or an external service, such as Cloud Container Engine (CCE) changes.
+
+
Differences Between Alarms and Events
- Alarms are reported when AOM or an external service, such as CCE is abnormal or may cause exceptions. Alarms must be handled. Otherwise, service exceptions may occur.
- Events generally carry some important information. They are reported when AOM or an external service, such as CCE encounters some changes. Such changes do not necessarily cause service exceptions. Events do not need to be handled.
+
+
Usage FAQs
+
+
+
diff --git a/docs/aom/umn/aom_03_0009.html b/docs/aom/umn/aom_03_0009.html
new file mode 100644
index 00000000..6b74ebd9
--- /dev/null
+++ b/docs/aom/umn/aom_03_0009.html
@@ -0,0 +1,66 @@
+
+
+What Is the Relationship Between the Time Range and Statistical Cycle?
+For Application Operations Management (AOM), a maximum of 1440 data points can be returned for a single metric query. The relationship between the time range and statistical cycle is as follows:
+
Maximum time range = Statistical cycle x 1440
+
If you select a time range shorter than or equal to the maximum time range, all the statistical cycles that meet the preceding formula can be selected. For example, if you query metrics in the last 1 hour, the available statistical cycles are 1 minute and 5 minutes.
+
Table 1 shows the relationship between the time range and statistical cycle.
+
+
Table 1 Relationship between the time range and statistical cycleTime Range
+ |
+Statistical Cycle
+ |
+
|---|
+
+Last 1 hour
+ |
+1 minute or 5 minutes
+ |
+
+Last 6 hours
+ |
+1 minute, 5 minutes, or 1 hour
+ |
+
+Last 1 day
+ |
+
+Last 7 days
+ |
+1 hour or 1 day
+ NOTE: 1 day is only for the metrics generated based on log statistical rules.
+
+ |
+
+Last 15 days
+ |
+1 hour or 1 day
+ NOTE: 1 day is only for the metrics generated based on log statistical rules.
+
+ |
+
+Last 30 days
+ |
+
+Last 3 months
+ |
+
+Last 6 months
+ |
+
+Last 9 months
+ |
+
+Last 12 months
+ |
+
+
+
+
+
What Can I Do If Resources Are Not Running Properly?
+The resource status includes Normal, Warning, Alarm, and Silent. Warning, Alarm, or Silent may result in resource exceptions. You can analyze and rectify exceptions based on the following suggestions.
+
Warning
If a minor alarm or warning exists, the resource status is Warning.
+
Suggestion: Handle problems based on alarm details.
+
+
Alarm
If a critical or major alarm exists, the resource status is Alarm.
+
Suggestion: Handle problems based on alarm details.
+
+
Silent
If the ICAgent fails to collect resource metrics, the resource status is Silent. The causes include but are not limited to:
+
- Cause 1: The ICAgent is abnormal.
Suggestion: In the navigation pane, choose Configuration Management > Agent Management. On the page that is displayed, check the ICAgent status. If the status is not Running, the ICAgent is not installed or abnormal. For details about how to solve the problem, see Table 1.
+
+
+
+
- Cause 2: AOM cannot monitor the current resource.
Suggestion: Check whether your resources can be monitored by AOM. Specifically, AOM can monitor hosts, Kubernetes containers, and user processes, but cannot monitor system processes.
+ - Cause 3: The resource is deleted or stopped.
Suggestion:
+- On the ECS page, check whether the host is restarted, stopped, or deleted.
- On the CCE page, check whether the service is stopped or deleted.
- If an application discovery rule is disabled or deleted, the application discovered based on the rule will also be disabled or deleted. Check whether the application discovery rule is disabled or deleted on AOM.
+
+
+
How Do I Set the Full-Screen Online Duration?
+AOM provides an automatic logout mechanism to secure customer information. Specifically, after you access a page on the console but do not perform any operations within 1 hour, the console automatically logs you out.
+
If you set a full-screen view in the AOM console and later the system logs you out, the full-screen view will also exit. In this case, real-time monitoring cannot be performed. AOM allows you to customize full-screen online duration, meeting various requirements.
+
Precautions
- For security purposes, exit the full-screen view when it is not required.
- The full-screen online duration is irrelevant to operations. If the preset duration times out, the login page is automatically displayed.
- The full-screen online duration is subject to the last setting.
For example, if full-screen monitoring is implemented on multiple screens, the online duration is subject to the last setting.
+For another example, if the online duration is set on both the O&M and Dashboard pages, the last setting prevails.
+ - The full-screen online duration takes precedence over the automatic logout mechanism of the cloud.
For example, if you log in to the console, set the full-screen online duration to 2 hours on AOM pages, and then open other pages, your setting on the AOM pages also takes effect on other pages. That is, the login page will be automatically displayed 2 hours later.
+ - If you leave all full-screen views, the default automatic logout mechanism is used.
For example, if you log in to the console, set the full-screen online duration to 2 hours on AOM pages, open other pages, and then leave all full-screen views of AOM, the default logout mechanism will be used. That is, if you do not perform any operations within 1 hour, the login page will be automatically displayed.
+
+
+
Setting the Full-Screen Online Duration on the Dashboard Page
- Log in to the AOM console. In the navigation pane, choose Overview > Dashboard.
- Click
in the upper right corner of the Dashboard page. In the dialog box that is displayed, set the full-screen online duration.
+ - Click OK to enter the full-screen view.
+
+
Does AOM Display Logs in Real Time?
+The logs displayed on Application Operations Management (AOM) are near real-time logs, of which the latency is in seconds.
+
There is a time interval between log collection and processing. If the number of logs is small, the latency is about 10s. If the number of logs is large, the latency is much longer.
+
How Do I Obtain an AK/SK?
+Each user can create a maximum of two Access Key ID/Secret Access Key (AK/SK) pairs. Once they are generated, they are permanently valid.
+
- AK: unique ID associated with the SK. It is used together with the SK to sign requests.
- SK: secret access key used in conjunction with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.
+
Procedure
- Log in to the management console, hover the mouse pointer over the username in the upper right corner, and select My Credentials from the drop-down list.
- On the My Credentials page, click the Access Keys tab.
- Click Create Access Key above the list, and enter the verification code or password.
- Click OK to download the generated AK/SK.
You can obtain the AK from the access key list and SK from the downloaded CSV file.
- Keep the CSV file properly. You can only download the file right after the access key is created. If you cannot find the file, you can create an access key again.
- Open the CSV file in the lower left corner, or choose Downloads in the upper right corner of the browser and open the CSV file.
- Keep your access keys secure and change them periodically for security purposes.
+
+
+
+
Consultation FAQs
+
+
+
diff --git a/docs/aom/umn/aom_03_0018.html b/docs/aom/umn/aom_03_0018.html
new file mode 100644
index 00000000..61ee7a2b
--- /dev/null
+++ b/docs/aom/umn/aom_03_0018.html
@@ -0,0 +1,11 @@
+
+
+Will Container Logs Be Deleted After They Are Dumped?
+
+
+
diff --git a/docs/aom/umn/aom_03_0020.html b/docs/aom/umn/aom_03_0020.html
new file mode 100644
index 00000000..deb955e9
--- /dev/null
+++ b/docs/aom/umn/aom_03_0020.html
@@ -0,0 +1,11 @@
+
+
+How Can I Check Whether a Service Is Available?
+Log in to the Application Operations Management (AOM) console, choose Container Monitoring in the navigation pane, and check the service status value at each time point in the workload monitoring view. If the value is 0, the service is normal. Otherwise, the service is abnormal.
+
User FAQs
+Why Is Monitoring Data Not Displayed in Real Time on the AOM Page After Resources Are Created?
After you create resources such as hosts, applications, components, and processes, the ICAgent reports their monitoring data every 10 minutes. Only when a report period ends, can monitoring data be displayed on the AOM page.
+
+
Why Is the Resource Status Displayed as Normal on the AOM Page After Resources Are Deleted?
After you delete a resource such as a host or workload from a Cloud Container Engine (CCE) cluster, the resource status is still Normal on the Host Monitoring or Container Monitoring page of AOM. This is normal. The status of the deleted resource will be changed to Deleted 30 minutes later.
+
+
What Can I Do If the ICAgent Fails to Be Upgraded?
In the custom cluster scenario, if the ICAgent fails to be upgraded, log in to the VM node and directly run the ICAgent installation command again.
+
Because the ICAgent supports overwriting installation, directly reinstall the ICAgent without uninstallation.
+
+
What Types of Log Files Can Be Collected?
If you specify a directory, all .log, .trace, and .out log files in this directory are collected by default. If you specify a log file, only this file is collected. The specified file must be a text file. Other types of log files, such as binary log files, cannot be collected.
+
+
Does the ICAgent Consume Lots of Resources Such as Memory and CPU?
- AOM collects basic metrics, including CPU and memory of VMs, containers, and processes.
Resource consumption: The resource consumption of the ICAgent is related to the number of containers and processes. In normal service traffic, the ICAgent consumes about 30 MB memory and 3% single-core CPU.
+Usage restriction: Ensure that the number of containers running on a single node is less than 1000.
+Protection mechanism:
- The ICAgent consumes a maximum of two CPU cores.
- When the memory consumed by the ICAgent exceeds min {4 GB, node physical memory/2}, AOM restarts the ICAgent for protection.
Min {4 GB, node physical memory/2} indicates the smaller value between 4 GB and node physical memory/2.
+
+
+
+ - AOM also collects log files, including syslog, standard container output, user configuration path, and container mounting files.
Resource consumption: The resource consumption of the ICAgent is closely related to the log volume, number of files, network bandwidth, and backend service processing capability.
+
+
+
How Does AOM Obtain a Custom Host IP Address on the Agent Management Page?
By default, AOM traverses all NICs on the VM and obtains the IP addresses of the Ethernet, bond, and wireless NICs based on priorities in descending order. To ensure that AOM obtains the IP address of a specific NIC, set the IC_NET_CARD=Desired NIC name environment variable when starting the ICAgent.
+
Example:
+
- Add export IC_NET_CARD=eth2 to /etc/profile.
- Run the source /etc/profile command to make the environment variable effective in the shell.
- Go to the /opt/oss/servicemgr/ICAgent/bin/manual/ directory, and stop and then restart the ICAgent.
bash mstop.sh
+bash mstart.sh
+ - Check whether the environment variable is properly transferred to the application.
strings /proc/{icagentprocid}/envrion | grep IC_NET_CARD
+
+
- If the IP address displayed on ICAgent is 127.0.0.1, the ICAgent may fail to obtain the local IP address during startup. This problem may occur when a VM is powered off and then restarted. To solve the problem, you only need to restart the ICAgent.
- If the IP address of your host changes (for example, a new IP address is allocated during renewal), the original IP address may be displayed on the agent management page. To solve the problem, you only need to restart the ICAgent.
+
+
+
What Can I Do If the ICAgent Fails to Be Installed in the Windows Environment and the "SERVICE STOP" Message Is Displayed?
Symptom: The ICAgent fails to be installed in the Windows environment and the "SERVICE STOP" message is displayed. No ICAgent task exists in the task manager. No ICAgent service exists in the system service list. When the sc query icagent command is executed, a message is displayed, indicating that no ICAgent is found.
+
Cause: Antivirus software, such as 360 Total Security, blocks registration of the ICAgent service.
+
Solution:
+
- Check whether antivirus software, such as 360 Total Security, is running.
- First close the antivirus software and install the ICAgent again.
+
In the Windows environment, manually add log collection paths. The ICAgent can collect .log, .trace, and .out files, but does not collect binary files or Windows system logs.
+
+
+
What Can I Do If the ICAgent Is Successfully Installed on ECS but Its Status Is Abnormal on the Agent Management Page?
The AK/SK is incorrect, or no agency is set when Installation Mode is set to Create Agency. Perform operations according to and install the ICAgent again.
+
+
Why Is the Status of an Alarm Rule Displayed as "Insufficient"?
+When you create an alarm rule for a resource, its data reported to AOM may be insufficient, as shown in the following figure.
+
Figure 1 Viewing the rule status
+
+
Possible causes:
+
- The data reporting latency is too large. That is, the difference between the latest data reporting time of the line graph and the current time is greater than one threshold reporting period, which can be set to 1 minute or 5 minutes. If no data is obtained within such a period, a message indicating insufficient data is displayed.
- If a metric is deleted or the host to which the metric belongs does not exist but the threshold rule still exists, a message indicating insufficient data is displayed.
+
Why the Status of a Workload that Runs Normally Is Displayed as "Abnormal" on the AOM Page?
+A workload runs normally on Cloud Container Engine (CCE), but its status is Abnormal on the AOM page.
+
+
Possible causes:
+
- The ICAgent version is too old.
ICAgent needs to be upgraded manually. If the ICAgent version is too old, the workload status may fail to be reported in time.
+If the displayed workload status is incorrect, first check whether the ICAgent is in the latest version on the Agent Management page.
+ - The node time is not synchronized with the actual time.
If the difference between the node time and the actual time is too large, the ICAgent fails to report metrics in time.
+If the displayed workload status is incorrect, check whether the node time is different from the actual time or check the NTP offset on the AOM page.
+
+
How Do I Create the apm_admin_trust Agency?
+Procedure
- Log in to the IAM console.
- In the navigation pane, choose Agencies.
- On the page that is displayed, click Create Agency in the upper right corner. The Create Agency page is displayed.
- Set parameters based on Table 1.
+
Table 1 Parameters for creating an agencyParameter
+ |
+Description
+ |
+Example
+ |
+
|---|
+
+Agency Name
+ |
+Set an agency name.
+ NOTE: The agency name must be apm_admin_trust.
+
+ |
+apm_admin_trust
+ |
+
+Agency Type
+ |
+Select Account.
+ |
+Common account
+ |
+
+Delegated Account
+ |
+Specify an account to delegate.
+ |
+op_svc_apm
+ |
+
+Validity Period
+ |
+Select Unlimited.
+ |
+Unlimited
+ |
+
+Description
+ |
+(Optional) Provide details about the agency.
+ |
+-
+ |
+
+
+
+
- On the Permissions area, click Assign Permissions.
- Add the following permissions: DMS User (or DMS UserAccess), CCE Administrator, and ECS User (or ECS CommonOperations), and select a region in Project [Region].
- Click OK.
+
+
Why Are Connection Channels Required?
+Different Virtual Private Clouds (VPCs) cannot communicate with each other. To solve this problem, create an application in the VPC where the data subscription application resides and set it to a VPC endpoint service. Then, create a VPC endpoint in the VPC where Distributed Message Service (DMS) resides. A connection channel can be established between the VPC endpoint and VPC endpoint service for communication.
+
What Can I Do If an ICAgent Is Offline?
+After an ICAgent is installed, its status is offline.
+
Problem Analysis
- Cause: The AK/SK are incorrect or ports 30200 and 30201 are disconnected.
- Impact: The ICAgent cannot work.
+
+
Solution
- Log in to the server where the ICAgent is installed as the root user.
- Run the following command to check whether the AK/SK configuration is correct:
cat /var/ICAgent/oss.icAgent.trace | grep proxyworkflow.go
+- If no command output is displayed, the AK/SK configuration is incorrect. Go to 3.
- If a command output is displayed, the AK/SK configuration is correct. Go to 4.
+ - After configuring the AK/SK, reinstall the ICAgent. If the installation still fails, go to 4.
- Check port connectivity.
- Run the following command to obtain the access IP address:
cat /opt/oss/servicemgr/ICAgent/envs/ICProbeAgent.properties | grep ACCESS_IP
+ - Run the following command to respectively check the connectivity of ports 30200 and 30201:
curl -k https://ACCESS_IP:30200
+curl -k https://ACCESS_IP:30201
+- If 404 is displayed, the port is connected. In this case, contact technical support.
- If the command output is not 404, the port is not connected. Contact the network administrator to open the port and reinstall the ICAgent. If the installation still fails, contact technical support.
+
+
+
+
Getting Started
+
+
+
+
+
diff --git a/docs/aom/umn/aom_06_0001.html b/docs/aom/umn/aom_06_0001.html
new file mode 100644
index 00000000..4b1b7715
--- /dev/null
+++ b/docs/aom/umn/aom_06_0001.html
@@ -0,0 +1,269 @@
+
+
+Restrictions
+OS Usage Restrictions
AOM supports multiple operating systems (OSs). When creating a host, ensure that its OS meets the requirements in Table 1. Otherwise, the host cannot be monitored by AOM.
+
+
Table 1 OSs and versions supported by AOMOS
+ |
+Version
+ |
+
|---|
+
+SUSE
+ |
+SUSE Enterprise 11 SP4 64-bit
+ |
+SUSE Enterprise 12 SP1 64-bit
+ |
+SUSE Enterprise 12 SP2 64-bit
+ |
+SUSE Enterprise 12 SP3 64-bit
+ |
+
+openSUSE
+ |
+13.2 64-bit
+ |
+42.2 64-bit
+ |
+15.0 64-bit (Currently, syslog logs cannot be collected.)
+ |
+
+EulerOS
+ |
+2.2 64-bit
+ |
+2.3 64-bit
+ |
+2.5 64-bit
+ |
+
+CentOS
+ |
+6.3 64-bit
+ |
+6.5 64-bit
+ |
+6.8 64-bit
+ |
+6.9 64-bit
+ |
+6.10 64-bit
+ |
+
+7.1 64-bit
+ |
+7.2 64-bit
+ |
+7.3 64-bit
+ |
+7.4 64-bit
+ |
+7.5 64-bit
+ |
+7.6 64-bit
+ |
+
+Ubuntu
+ |
+14.04 server 64-bit
+ |
+16.04 server 64-bit
+ |
+18.04 server 64-bit
+ |
+
+Fedora
+ |
+24 64-bit
+ |
+25 64-bit
+ |
+29 64-bit
+ |
+
+Debian
+ |
+7.5.0 32-bit
+ |
+7.5.0 64-bit
+ |
+8.2.0 64-bit
+ |
+8.8.0 64-bit
+ |
+9.0.0 64-bit
+ |
+
+
+
+
+
- For Linux x86_64 servers, AOM supports all the OSs and versions listed in the preceding table.
- For Linux Arm servers, AOM only supports CentOS 7.4 and later versions, and other OSs and versions listed in the preceding table.
+
+
+
Resource Usage Restrictions
When using AOM, learn about the restrictions in Table 2.
+
+
Table 2 Resource usage restrictionsCategory
+ |
+Object
+ |
+Usage Restrictions
+ |
+
|---|
+
+Dashboard
+ |
+Dashboard
+ |
+A maximum of 50 dashboards can be created in a region.
+ |
+
+Graph in a dashboard
+ |
+A maximum of 20 graphs can be added to a dashboard.
+ |
+
+Number of resources, threshold rules, components, or hosts in a graph
+ |
+- A maximum of 100 resources across clusters can be added to a line graph.
- Only one resource can be added to a digit graph.
- A maximum of 10 threshold rules can be added to a threshold status graph.
- A maximum of 10 hosts can be added to a host status graph.
- A maximum of 10 components can be added to a component status graph.
+ |
+
+Metric
+
+ |
+Metric data
+ |
+Metric data can be stored in the database for up to 30 days.
+ |
+
+Total number of metrics
+ |
+Up to 400,000 for a single account.
+Up to 100,000 for a small specification.
+
+ |
+
+Metric item
+ |
+After resources such as clusters, components, and hosts are deleted, their related metrics can be stored in the database for a maximum of 30 days.
+ |
+
+Dimension
+ |
+A maximum of 20 dimensions can be configured for a metric.
+ |
+
+Metric query API
+ |
+A maximum of 20 metrics can be queried at a time.
+ |
+
+Statistical period
+ |
+The maximum statistical period is 1 hour.
+ |
+
+Data points returned for a single query
+ |
+A maximum of 1440 data points can be returned each time.
+ |
+
+Custom metric
+ |
+Unlimited.
+ |
+
+Custom metric to be reported
+ |
+A single request cannot exceed 40 KB. The timestamp of a reported metric cannot 10 minutes later than the standard UTC time. In addition, out-of-order metrics are not received. That is, if a metric is reported at a certain time point, the metrics of earlier time points cannot be reported.
+ |
+
+Application metric
+ |
+- When the number of containers on a host exceeds 1000, the ICAgent stops collecting application metrics and sends the ICAgent Stopped Collecting Application Metrics alarm (ID: 34105).
- When the number of containers on a host is less than 1000, the ICAgent resumes the collection of application metrics and the ICAgent Stopped Collecting Application Metrics alarm is cleared.
+ |
+
+Resources consumed by the ICAgent
+ |
+When the ICAgent collects basic metrics, the resources consumed by the ICAgent are greatly affected by the number of containers and processes. On a VM without any services, the ICAgent consumes 30 MB memory and records 1% CPU usage. To ensure collection reliability, ensure that the number of containers running on a single node must be less than 1000.
+ |
+
+Log
+
+ |
+Size of a log
+ |
+The maximum size of each log is 10 KB. If a log exceeds 10 KB, the ICAgent does not collect it. That is, the log will be discarded.
+ |
+
+Log traffic
+ |
+A maximum of 10 MB/s is supported for each tenant in a region. If the log traffic exceeds 10 MB/s, logs may be lost.
+ |
+
+|
+ Log file
+ |
+Only text log files can be collected. Other types of log files, such as binary files, cannot be collected.
+ |
+
+The ICAgent can collect a maximum of 20 log files from a volume mounting directory.
+ |
+
+The ICAgent can collect a maximum of 1000 standard container output log files. These files must be in JSON format.
+ |
+
+Resources consumed during log file collection
+ |
+The resources consumed during log file collection are closely related to the log volume, number of files, network bandwidth, and backend service processing capability.
+ |
+
+Log loss
+ |
+ICAgent uses multiple mechanisms to ensure log collection reliability and prevent data loss. However, logs may be lost in the following scenarios:
+- The log rotation policy of Cloud Container Engine (CCE) is not used.
- Log files are rotated at a high speed, for example, once per second.
- Logs cannot be forwarded due to improper system security settings or syslog itself.
- The container running time, for example, shorter than 30s, is extremely short.
- A single node generates logs at a high speed, exceeding the allowed transmit bandwidth or log collection speed. Ensure that the log generation speed of a single node is lower than 5 MB/s.
+ |
+
+Log loss
+ |
+When a single log line exceeds 10,240 bytes, the line will be discarded.
+ |
+
+Log repetition
+ |
+When the ICAgent is restarted, identical data may be collected around the restart time.
+ |
+
+Alarm
+ |
+Alarm
+ |
+You can query the alarms generated in the last 15 days.
+ |
+
+Event
+ |
+You can query the events generated in the last 15 days.
+ |
+
+-
+ |
+Application discovery rule
+ |
+You can create a maximum of 100 application discovery rules.
+ |
+
+
+
+
+
+
Service Usage Restrictions
If the AMS-Access service is powered off or restarted unexpectedly when you use AOM, a metric data breakpoint occurs on some resources such as hosts, components, and containers in a collection period. This breakpoint is visible on the monitoring page and has no impacts. To avoid breakpoints in a metric graph, set the value of Interpolation Mode to 0 or average on the Metric Monitoring page. In this way, the system automatically replaces breakpoints with 0 or average values, as shown in Figure 1.
+
Figure 1 Changing the interpolation mode
+
+
Basic Concepts
+Metrics
Metrics reflect resource performance data or status. A metric consists of a namespace, dimension, name, and unit.
+
Metric namespaces can be regarded as containers for storing metrics. Metrics in different namespaces are independent of each other so that metrics of different applications will not be aggregated to the same statistics information. Each metric has certain features, and a dimension may be considered as a category of such features. Figure 1 describes the relationships among namespaces, dimensions, and cluster metrics.
+
Figure 1 Cluster metrics
+
+
Hosts
Each host of AOM corresponds to a VM or physical machine. A host can be your own VM or physical machine, or a VM (for example, an ECS) that you created. A host can only be connected to AOM for monitoring when its OS is supported by AOM and an ICAgent has been installed on the host.
+
+
ICAgent
ICAgent is the collector of AOM. It runs on hosts to collect metrics, logs, and application performance data in real time. Before using AOM, ensure that the ICAgent has been installed. Otherwise, AOM cannot be used.
+
+
Logs
AOM supports log collection, search, analysis, download, and dump. It also reports alarms based on keyword statistics and enables you to export reports, query SQL statements, and monitor data in real time.
+
+
Alarms
Alarms are reported when AOM or an external service such as or Cloud Container Engine (CCE) is abnormal or may cause exceptions. Alarms will cause service exceptions and need to be handled.
+
There are two alarm clearance modes:
+
- Automatic clearance: After a fault is rectified, AOM automatically clears the corresponding alarm, for example, a threshold alarm.
- Manual clearance: After a fault is rectified, AOM does not automatically clear the corresponding alarm, for example, ICAgent installation failure alarm. In such a case, manually clear the alarm.
+
+
Events
Events generally carry some important information. They are reported when AOM or an external service, such as or CCE encounters some changes. Such changes do not necessarily cause service exceptions. Events do not need to be handled.
+
+
Application Scenarios
+Problem Inspection and Demarcation
During routine O&M, it is hard to locate faults and obtain logs. Therefore, a monitoring platform is required to monitor resources, logs, and application performance.
+
AOM interconnects with application services, and collects O&M data of infrastructures, middleware, and application instances in one stop. Through metric monitoring, log analysis, and alarm reporting, AOM enables you to monitor the application running status and resource usage easily, and detect and demarcate problems in a timely manner.
+
Advantages
+
- Automatic discovery of applications: Collectors are deployed to proactively discover and monitor applications based on different runtime environments.
- Monitoring of distributed applications: AOM serves as a unified O&M platform that enables you to implement multi-dimensional monitoring over distributed applications with multiple cloud services.
- Alarm notification: Multiple exception detection policies, alarm trigger modes, and APIs are provided.
+
Figure 1 Problem inspection and demarcation
+
+
Multi-Dimensional O&M
You need to monitor comprehensive system running status and make fast response to various problems.
+
AOM provides multi-dimensional O&M capabilities from the cloud level to the resource level and from application monitoring to microservice tracing.
+
Advantages
+
- User experience assurance: Service health status KPIs in real time are monitored in real time and root causes of exceptions are analyzed.
- Fast fault diagnosis: Distributed call tracing enables you to locate faults quickly.
- Resource running assurance: Hundreds of O&M metrics about resources such as containers, disks, and networks are monitored in real time, and clusters, VMs, applications, and containers are associated for analysis.
+
Figure 2 Multi-dimensional O&M
+
+
Functions
+Application Monitoring
Application monitoring allows you to view application resource usage, trends, and alarms in real time, so that you can make fast responses to ensure smooth running for applications.
+
This function adopts the hierarchical drill-down design. The hierarchy is as follows: Application list > Application details > Component details > Instance details > Process details. Applications, components, instances, and processes are visually associated with each other on the console.
+
+
Host Monitoring
Host monitoring allows you to view host resource usage, trends, and alarms in real time, so that you can make fast responses and ensure smooth running for hosts.
+
Like application monitoring, this function also adopts the hierarchical drill-down design. The hierarchy is as follows: Host list > Host details. The details page contains all the instances, GPUs, NICs, disks, and file systems of the current host.
+
+
Automatic Discovery of Applications
After you deploy applications on hosts, the ICAgent installed on the hosts automatically collects information, including names of processes, components, containers, and Kubernetes pods. Applications are automatically discovered and their graphs are displayed on the console. You can then set aliases and groups for better resource management.
+
+
Dashboard
With a dashboard, different graphs can be displayed on the same screen. Various graphs, such as line graphs, digit graphs, and top N resource graphs enable you to monitor data comprehensively.
+
For example, you can add key metrics to a dashboard for real-time monitoring. You can also compare the same metric of different resources on one screen. In addition, by adding common O&M metrics to a dashboard, you do not need to reselect them when re-opening the AOM console during routine O&M.
+
+
Alarm Management
The alarm list helps you manage alarms and events.
+
You can create threshold rules for key resource metrics. When the metric value reaches the threshold, AOM will generate alarms.
+
+
Log Management
AOM provides powerful log management capabilities. Log search enables you to quickly search for required logs from massive quantities of logs. Log dump enables you to store logs for a long time. After you create statistical rules, AOM can periodically count keywords in logs and generate metric data, so that you can monitor system performance and services in real time. By configuring delimiters, you can divide log content into multiple words and use these words to search for logs.
+
+
What Is AOM?
+Challenges
With the popularization of container technologies, lots of enterprises develop applications using microservice frameworks. Because the number of cloud services increases, enterprises gradually turn to cloud O&M. However, they face the following O&M challenges:
+
Figure 1 Existing O&M issues
+
- Cloud O&M has high requirements on personnel skills. O&M tools are hard to configure. Multiple systems need to be maintained at the same time. Distributed tracing systems face high learning and usage costs, but have poor stability.
- Distributed applications face analysis difficulties such as how to visualize the dependency between microservices, improve user experience, associate scattered logs for analysis, and quickly trace problems.
+
+
Introduction to AOM
Figure 2 One-stop O&M platform
+
Application Operations Management (AOM) is a one-stop, multi-dimensional O&M management platform for cloud applications. It monitors your applications and related cloud resources, analyzes application health status in real time, and provides flexible data visualization functions, helping you monitor running status of applications, resources, and services in real time and detect faults in a timely manner.
+
+
Advantages
Figure 3 AOM advantage 1
+
Figure 4 AOM advantage 2
+
- Management over massive quantities of logs
AOM supports log search and service analysis, automatically associates logs for cluster analysis, and filters logs by application, host, file, or instance.
+ - Association analysis
AOM automatically associates applications and resources and displays data in a panorama view. Through analysis of metrics and alarms about applications, components, instances, hosts, and transactions, AOM allows you to easily locate faults.
+ - Open ecosystem
O&M data query APIs are opened, collection standards are provided, and independent development is supported.
+
+
+
Metric Overview
+
+
+
diff --git a/docs/aom/umn/aom_06_0008.html b/docs/aom/umn/aom_06_0008.html
new file mode 100644
index 00000000..8659b62c
--- /dev/null
+++ b/docs/aom/umn/aom_06_0008.html
@@ -0,0 +1,11 @@
+
+
+Service Metrics and Dimensions
+Service metrics consist of instance metrics. The dimensions of service metrics are the same as those of instance metrics. For details, see Instance Metrics and Dimensions.
+
Host Metrics and Dimensions
+
+
Table 1 Host metricsMetric
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+
|---|
+
+Total CPU cores (aom_node_cpu_limit_core)
+ |
+Total number of CPU cores that have been applied for a measured object
+ |
+≥ 1
+ |
+Cores
+ |
+
+Used CPU cores (aom_node_cpu_used_core)
+ |
+Number of CPU cores used by a measured object
+ |
+≥ 0
+ |
+Cores
+ |
+
+CPU usage (aom_node_cpu_usage)
+ |
+CPU usage of a measured object
+ |
+0–100
+ |
+%
+ |
+
+Available physical memory (aom_node_memory_free_megabytes)
+ |
+Available physical memory of a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Available virtual memory (aom_node_virtual_memory_free_megabytes)
+ |
+Available virtual memory of a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Total GPU memory (aom_node_gpu_memory_free_megabytes)
+ |
+Total GPU memory of a measured object
+ |
+> 0
+ |
+MB
+ |
+
+GPU memory usage (aom_node_gpu_memory_usage)
+ |
+Percentage of the used GPU memory to the total GPU memory
+ |
+0–100
+ |
+%
+ |
+
+Used GPU memory (aom_node_gpu_memory_used_megabytes)
+ |
+GPU memory used by a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+GPU usage (aom_node_gpu_usage)
+ |
+GPU usage of a measured object
+ |
+0–100
+ |
+%
+ |
+
+Physical memory usage (aom_node_memory_usage)
+ |
+Percentage of the used physical memory to the total physical memory
+ |
+0–100
+ |
+%
+ |
+
+Host status (aom_node_status)
+ |
+Host status
+ |
+
+ |
+N/A
+ |
+
+NTP offset (aom_node_ntp_offset_ms)
+ |
+Offset between the local time of the host and the NTP server time. The closer the NTP offset is to 0, the closer the local time of the host is to the time of the NTP server.
+ |
+-
+ |
+ms
+ |
+
+NTP server status (aom_node_ntp_server_status)
+ |
+Whether the host is connected to the NTP server
+ |
+0 or 1
+- 0: Connected
- 1: Unconnected
+ |
+N/A
+ |
+
+NTP synchronization status (aom_node_ntp_status)
+ |
+Whether the local time of the host is synchronized with the NTP server time
+ |
+0 or 1
+- 0: Synchronous
- 1: Not synchronized
+ |
+N/A
+ |
+
+Processes (aom_node_process_number)
+ |
+Number of processes on a measured object
+ |
+≥ 0
+ |
+N/A
+ |
+
+GPU temperature (aom_node_gpu_temperature_centigrade)
+ |
+GPU temperature of a measured object
+ |
+-
+ |
+°C
+ |
+
+Total physical memory (aom_node_memory_total_megabytes)
+ |
+Total physical memory that has been applied for a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Total virtual memory (aom_node_virtual_memory_total_megabytes)
+ |
+Total virtual memory that has been applied for a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Virtual memory usage (aom_node_virtual_memory_usage)
+ |
+Percentage of the used virtual memory to the total virtual memory
+ |
+0–100
+ |
+%
+ |
+
+Threads (aom_node_current_threads_num)
+ |
+Number of threads created on a host
+ |
+≥ 0
+ |
+N/A
+ |
+
+Max. threads (aom_node_sys_max_threads_num)
+ |
+Maximum number of threads that can be created on a host
+ |
+≥ 0
+ |
+N/A
+ |
+
+Total physical disk space (aom_node_phy_disk_total_capacity_megabytes)
+ |
+Total disk space of a host
+ |
+≥ 0
+ |
+MB
+ |
+
+Used disk space (aom_node_physical_disk_total_used_megabytes)
+ |
+Used disk space of a host
+ |
+≥ 0
+ |
+MB
+ |
+
+Hosts (aom_billing_hostUsed)
+ |
+Number of hosts connected per day
+ |
+≥ 0
+ |
+N/A
+ |
+
+
+
+
+
- Memory usage = (Physical memory capacity – Available physical memory capacity)/Physical memory capacity; Virtual memory usage = ((Physical memory capacity + Total virtual memory capacity) – (Available physical memory capacity + Available virtual memory capacity))/(Physical memory capacity + Total virtual memory capacity)
- The virtual memory of a VM is 0 MB by default. If no virtual memory is configured, the memory usage on the monitoring page is the same as the virtual memory usage.
- For the total and used physical disk space, only the space of the local disk partitions' file systems is counted. The file systems (such as JuiceFS, NFS, and SMB) mounted to the host through the network are not taken into account.
+
+
+
Table 2 Dimensions of host metricsDimension
+ |
+Description
+ |
+
|---|
+
+clusterId
+ |
+Cluster ID
+ |
+
+clusterName
+ |
+Cluster name
+ |
+
+gpuName
+ |
+GPU name
+ |
+
+gpuID
+ |
+GPU ID
+ |
+
+npuName
+ |
+NPU name
+ |
+
+npuID
+ |
+NPU ID
+ |
+
+hostID
+ |
+Host ID
+ |
+
+nameSpace
+ |
+Cluster namespace
+ |
+
+nodeIP
+ |
+Host IP address
+ |
+
+hostName
+ |
+Host name
+ |
+
+
+
+
+
Cluster Metrics and Dimensions
+ Cluster metrics are aggregated by AOM based on host metrics, and do not include the metrics of master nodes.
+
+
+
Table 1 Cluster metricsMetric
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+
|---|
+
+Total CPU cores (aom_cluster_cpu_limit_core)
+ |
+Total number of CPU cores that have been applied for a measured object
+ |
+≥ 1
+ |
+Cores
+ |
+
+Used CPU cores (aom_cluster_cpu_used_core)
+ |
+Number of CPU cores used by a measured object
+ |
+≥ 0
+ |
+Cores
+ |
+
+CPU usage (aom_cluster_cpu_usage)
+ |
+CPU usage of a measured object
+ |
+0–100
+ |
+%
+ |
+
+Available disk space (aom_cluster_disk_available_capacity_megabytes)
+ |
+Disk space that has not been used
+ |
+≥ 0
+ |
+MB
+ |
+
+Total disk space (aom_cluster_disk_capacity_megabytes)
+ |
+Total disk space
+ |
+≥ 0
+ |
+MB
+ |
+
+Disk usage (aom_cluster_disk_usage)
+ |
+Percentage of the used disk space to the total disk space
+ |
+0–100
+ |
+%
+ |
+
+Available physical memory (aom_cluster_memory_free_megabytes)
+ |
+Available physical memory of a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Available virtual memory (aom_cluster_virtual_memory_free_megabytes)
+ |
+Available virtual memory of a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Available GPU memory (aom_cluster_gpu_memory_free_megabytes)
+ |
+Available GPU memory of a measured object
+ |
+> 0
+ |
+MB
+ |
+
+GPU memory usage (aom_cluster_gpu_memory_usage)
+ |
+Percentage of the used GPU memory to the total GPU memory
+ |
+0–100
+ |
+%
+ |
+
+Used GPU memory (aom_cluster_gpu_memory_used_megabytes)
+ |
+GPU memory used by a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+GPU usage (aom_cluster_gpu_usage)
+ |
+GPU usage of a measured object
+ |
+0–100
+ |
+%
+ |
+
+Physical memory usage (aom_cluster_memory_usage)
+ |
+Percentage of the used physical memory to the total physical memory
+ |
+0–100
+ |
+%
+ |
+
+Downlink rate (BPS) (aom_cluster_network_receive_bytes)
+ |
+Inbound traffic rate of a measured object
+ |
+≥ 0
+ |
+Byte/s
+ |
+
+Uplink rate (BPS) (aom_cluster_network_transmit_bytes)
+ |
+Outbound traffic rate of a measured object
+ |
+≥ 0
+ |
+Byte/s
+ |
+
+Total physical memory (aom_cluster_memory_total_megabyte)
+ |
+Total physical memory that has been applied for a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Total virtual memory (aom_cluster_virtual_memory_total_megabytes)
+ |
+Total virtual memory that has been applied for a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Virtual memory usage (aom_cluster_virtual_memory_usage)
+ |
+Percentage of the used virtual memory to the total virtual memory
+ |
+0–100
+ |
+%
+ |
+
+
+
+
+
+
Table 2 Dimensions of cluster metricsDimension
+ |
+Description
+ |
+
|---|
+
+clusterId
+ |
+Cluster ID
+ |
+
+clusterName
+ |
+Cluster name
+ |
+
+projectId
+ |
+Project ID
+ |
+
+
+
+
+
Relationships Between AOM and Other Services
+AOM can work with Distributed Message Service (DMS), and Cloud Trace Service (CTS). When AOM interconnects with middleware services such as Virtual Private Cloud (VPC) and Elastic Load Balance (ELB), you can monitor them in AOM. When AOM interconnects with Cloud Container Engine (CCE) or Cloud Container Instance (CCI), you can monitor their basic resources and applications, and view related logs and alarms.
+
OBS
Object Storage Service (OBS) is a secure, reliable, and cost-effective cloud storage service. With OBS, you can easily create, modify, and delete buckets, as well as upload, download, and delete objects.
+
AOM allows you to dump logs to OBS buckets for long-term storage.
+
+
CTS
CTS records operations on cloud resources in your account. Based on the records, you can perform security analysis, monitor resource changes, conduct compliance audits, and locate faults. To store operation records for a longer time, you can subscribe to OBS and synchronize operation records to OBS in real time.
+
With CTS, you can record operations associated with AOM for future query, audit, and tracing.
+
+
IAM
Identity and Access Management (IAM) provides identity authentication, permission management, and access control.
+
IAM can implement authentication and fine-grained authorization for AOM.
+
+
Cloud Eye
Cloud Eye provides a multi-dimensional monitoring platform for resources such as Elastic Cloud Server (ECS) and bandwidth. With Cloud Eye, you can view the resource usage and service running status in the cloud, and respond to exceptions in a timely manner to ensure that services run smoothly.
+
+
VPC
VPC is a logically isolated virtual network. It is created for ECSs, and supports custom configuration and management, improving resource security and simplifying network deployment.
+
+
ELB
ELB distributes access traffic to multiple backend ECSs based on forwarding policies. By distributing traffic, ELB expands the capabilities of application systems to provide services externally. By preventing single points of failures, ELB improves the availability of application systems.
+
+
RDS
Relational Database Service (RDS) is a cloud-based web service that is reliable, scalable, and easy to manage.
+
+
DCS
DCS is an online, distributed, in-memory cache service compatible with Redis, Memcached, and In-Memory Data Grid (IMDG). It is reliable, scalable, ready to use out-of-the-box, and easy to manage, meeting your requirements for high read/write performance and fast data access.
+
+
CCE
CCE is a high-performance and scalable container service through which enterprises can build reliable containerized applications. It integrates network and storage capabilities, and is compatible with Kubernetes and Docker container ecosystems. CCE enables you to create and manage diverse containerized workloads easily. It also provides efficient O&M capabilities, such as container fault self-healing, monitoring log collection, and auto scaling.
+
You can monitor basic resources, applications, logs, and alarms about CCE on the AOM console.
+
+
FunctionGraph
FunctionGraph hosts and computes functions in a serverless context. It automatically scales up/down resources during peaks and spikes without requiring the reservation of dedicated servers or capacities. Resources are billed on a pay-per-use basis.
+
You can monitor basic resources, applications, logs, and alarms about FunctionGraph on the AOM console.
+
+
ECS
ECS is a computing server consisting of the CPU, memory, image, and Elastic Volume Service (EVS) disk. It supports on-demand allocation and auto scaling. ECSs integrate VPC, virtual firewall, and multi-data-copy capabilities to create an efficient, reliable, and secure computing environment. This ensures stable and uninterrupted running of services. After creating an ECS server, you can use it like using your local computer or physical server.
+
When purchasing an ECS, ensure that its OS meets the requirements in Table 1. In addition, install an ICAgent on the ECS. Otherwise, the ECS cannot be monitored by AOM. You can monitor basic resources, applications, logs, and alarms about this ECS on the AOM console.
+
+
BMS
Bare Metal Server (BMS) is a dedicated physical server in the cloud. It provides high-performance computing and ensures data security for core databases, key application systems, and big data. With the advantage of scalable cloud resources, you can apply for BMS servers flexibly and they are billed on a pay-per-use basis.
+
When purchasing a BMS server, ensure that its OS meets the requirements in Table 1. In addition, install an ICAgent on the server. Otherwise, the server cannot be monitored by AOM. You can monitor basic resources, applications, logs, and alarms about this server on the AOM console.
+
+
Product Architecture
+AOM is a multi-dimensional O&M platform that focuses on resource data and associates log, metric, resource, alarm, and event data. It consists of the data collection and access layer, transmission and storage layer, and service computing layer.
+
Architecture Description
+
+
Introduction
+Metrics reflect resource performance data or status. A metric consists of a namespace, dimension, name, and unit. Metrics can be divided into:
+
- System metrics: basic metrics provided by AOM, such as CPU usage and used CPU cores.
- Custom metrics: user-defined metrics. Custom metrics can be reported using the following methods:
- Method 1: Use AOM APIs. For details, see "Adding Monitoring Data" and "Querying Monitoring Data" in the Application Operations Management (AOM) API Reference.
- Method 2: When creating containerized applications on CCE, interconnect with Prometheus to report custom metrics. For details, see "Custom Monitoring" in Cloud Container Engine (CCE) User Guide.
+
+
Metric Namespaces
A namespace is an abstract collection of resources and objects. Metrics in different namespaces are independent of each other so that metrics of different applications will not be aggregated to the same statistics information.
+
- Namespaces of system metrics are fixed and started with PAAS.. For details, see Table 1.
+
Table 1 Namespaces of system metricsNamespace
+ |
+Description
+ |
+
|---|
+
+PAAS.AGGR
+ |
+Namespace of cluster metrics
+ |
+
+PAAS.NODE
+ |
+Namespace of host, network, disk, and file system metrics
+ |
+
+PAAS.CONTAINER
+ |
+Namespace of component, instance, process, and container metrics
+ |
+
+
+
+
+
- Namespaces of custom metrics must be in the XX.XX format. Each namespace must be 3 to 32 characters long, starting with a letter (excluding PAAS., SYS., and SRE.). Only digits, letters, and underscores (_) are allowed.
+
+
Metric Dimensions
Metric dimensions indicate the categories of metrics. Each metric has certain features, and a dimension may be considered as a category of such features.
+
- Dimensions of system metrics are fixed. Different types of metrics have different dimensions. For more details, see the following sections.
- Dimensions of custom metrics must be 1 to 32 characters long, which need to be customized.
+
+
Network Metrics and Dimensions
+
+
Table 1 Network metricsMetric
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+
|---|
+
+Downlink rate (BPS) (aom_node_network_receive_bytes)
+ |
+Inbound traffic rate of a measured object
+ |
+≥ 0
+ |
+Byte/s
+ |
+
+Downlink rate (PPS) (aom_node_network_receive_packets)
+ |
+Number of data packets received by an NIC per second
+ |
+≥ 0
+ |
+Packet/s
+ |
+
+Downlink error rate (aom_node_network_receive_error_packets)
+ |
+Number of error packets received by an NIC per second
+ |
+≥ 0
+ |
+Count/s
+ |
+
+Uplink rate (BPS) (aom_node_network_transmit_bytes)
+ |
+Outbound traffic rate of a measured object
+ |
+≥ 0
+ |
+Byte/s
+ |
+
+Uplink error rate (aom_node_network_transmit_error_packets)
+ |
+Number of error packets sent by an NIC per second
+ |
+≥ 0
+ |
+Count/s
+ |
+
+Uplink rate (PPS) (aom_node_network_transmit_packets)
+ |
+Number of data packets sent by an NIC per second
+ |
+≥ 0
+ |
+Packet/s
+ |
+
+Total rate (BPS) (aom_node_network_total_bytes)
+ |
+Total inbound and outbound traffic rate of a measured object
+ |
+≥ 0
+ |
+Byte/s
+ |
+
+
+
+
+
+
Table 2 Dimensions of network metricsDimension
+ |
+Description
+ |
+
|---|
+
+clusterId
+ |
+Cluster ID
+ |
+
+hostID
+ |
+Host ID
+ |
+
+nameSpace
+ |
+Cluster namespace
+ |
+
+netDevice
+ |
+NIC name
+ |
+
+nodeIP
+ |
+Host IP address
+ |
+
+nodeName
+ |
+Host name
+ |
+
+
+
+
+
Disk Metrics and Dimensions
+
+
Table 1 Disk metricsMetric
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+
|---|
+
+Disk read rate (aom_node_disk_read_kilobytes)
+ |
+Volume of data read from a disk per second
+ |
+≥ 0
+ |
+KB/s
+ |
+
+Disk write rate (aom_node_disk_write_kilobytes)
+ |
+Volume of data written into a disk per second
+ |
+≥ 0
+ |
+KB/s
+ |
+
+
+
+
+
+
Table 2 Dimensions of disk metricsDimension
+ |
+Description
+ |
+
|---|
+
+clusterId
+ |
+Cluster ID
+ |
+
+diskDevice
+ |
+Disk name
+ |
+
+hostID
+ |
+Host ID
+ |
+
+nameSpace
+ |
+Cluster namespace
+ |
+
+nodeIP
+ |
+Host IP address
+ |
+
+nodeName
+ |
+Host name
+ |
+
+
+
+
+
File System Metrics and Dimensions
+
+
Table 1 File system metricsMetric
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+
|---|
+
+Available disk space (aom_node_disk_available_capacity_megabytes)
+ |
+Disk space that has not been used
+ |
+≥ 0
+ |
+MB
+ |
+
+Total disk space (aom_node_disk_capacity_megabytes)
+ |
+Total disk space
+ |
+≥ 0
+ |
+MB
+ |
+
+Disk read/write status (aom_node_disk_rw_status)
+ |
+Read or write status of a disk
+ |
+0 or 1
+- 0: read/write
- 1: read-only
+ |
+N/A
+ |
+
+Disk usage (aom_node_disk_usage)
+ |
+Percentage of the used disk space to the total disk space
+ |
+0–100
+ |
+%
+ |
+
+
+
+
+
+
Table 2 Dimensions of file system metricsDimension
+ |
+Description
+ |
+
|---|
+
+clusterId
+ |
+Cluster ID
+ |
+
+clusterName
+ |
+Cluster name
+ |
+
+fileSystem
+ |
+File system
+ |
+
+hostID
+ |
+Host ID
+ |
+
+mountPoint
+ |
+Mount point
+ |
+
+nameSpace
+ |
+Cluster namespace
+ |
+
+nodeIP
+ |
+Host IP address
+ |
+
+nodeName
+ |
+Host name
+ |
+
+
+
+
+
Container Metrics and Dimensions
+
+
Table 1 Container metricsMetric
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+
|---|
+
+Total CPU cores (aom_container_cpu_limit_core)
+ |
+Total number of CPU cores restricted for a measured object
+ |
+≥ 1
+ |
+Cores
+ |
+
+Used CPU cores (aom_container_cpu_used_core)
+ |
+Number of CPU cores used by a measured object
+ |
+≥ 0
+ |
+Cores
+ |
+
+CPU usage (aom_container_cpu_usage)
+ |
+CPU usage of a measured object. That is, the percentage of the used CPU cores to the total CPU cores restricted for a measured object.
+ |
+0–100
+ |
+%
+ |
+
+Disk read rate (aom_container_disk_read_kilobytes)
+ |
+Volume of data read from a disk per second
+ |
+≥ 0
+ |
+KB/s
+ |
+
+Disk write rate (aom_container_disk_write_kilobytes)
+ |
+Volume of data written into a disk per second
+ |
+≥ 0
+ |
+KB/s
+ |
+
+Available file system capacity (aom_container_filesystem_available_capacity_megabytes)
+ |
+Available file system capacity of a measured object. This metric is available only for containers using the Device Mapper storage drive in the Kubernetes cluster of version 1.11 or later.
+ |
+≥ 0
+ |
+MB
+ |
+
+Total file system capability (aom_container_filesystem_capacity_megabytes)
+ |
+Total file system capacity of a measured object. This metric is available only for containers using the Device Mapper storage drive in the Kubernetes cluster of version 1.11 or later.
+ |
+≥ 0
+ |
+MB
+ |
+
+File system usage (aom_container_filesystem_usage)
+ |
+File system usage of a measured object. That is, the percentage of the used file system to the total file system. This metric is available only for containers using the Device Mapper storage drive in the Kubernetes cluster of version 1.11 or later.
+ |
+0–100
+ |
+%
+ |
+
+Total GPU memory (aom_container_gpu_memory_free_megabytes)
+ |
+Total GPU memory of a measured object
+ |
+> 0
+ |
+MB
+ |
+
+GPU memory usage (aom_container_gpu_memory_usage)
+ |
+Percentage of the used GPU memory to the total GPU memory
+ |
+0–100
+ |
+%
+ |
+
+Used GPU memory (aom_container_gpu_memory_used_megabytes)
+ |
+GPU memory used by a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+GPU usage (aom_container_gpu_usage)
+ |
+GPU usage of a measured object
+ |
+0–100
+ |
+%
+ |
+
+Total NPU memory (aom_container_npu_memory_free_megabytes)
+ |
+Total NPU memory of a measured object
+ |
+> 0
+ |
+MB
+ |
+
+NPU memory usage (aom_container_npu_memory_usage)
+ |
+Percentage of the used NPU memory to the total NPU memory
+ |
+0–100
+ |
+%
+ |
+
+Used NPU memory (aom_container_npu_memory_used_megabytes)
+ |
+NPU memory used by a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+NPU usage (aom_container_npu_usage)
+ |
+NPU usage of a measured object
+ |
+0–100
+ |
+%
+ |
+
+Total physical memory (aom_container_memory_request_megabytes)
+ |
+Total physical memory restricted for a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Physical memory usage (aom_container_memory_usage)
+ |
+Percentage of the used physical memory to the total physical memory restricted for a measured object
+ |
+0–100
+ |
+%
+ |
+
+Used physical memory (aom_container_memory_used_megabytes)
+ |
+Used physical memory of a measured object
+ NOTE: If the cluster version is 1.2.1 or later, this metric indicates the used working set memory and is equivalent to container_memory_working_set_bytes on the CCE console.
+
+ |
+≥ 0
+ |
+MB
+ |
+
+Downlink rate (BPS) (aom_container_network_receive_bytes)
+ |
+Inbound traffic rate of a measured object
+ |
+≥ 0
+ |
+Byte/s
+ |
+
+Downlink rate (PPS) (aom_container_network_receive_packets)
+ |
+Number of data packets received by an NIC per second
+ |
+≥ 0
+ |
+Packet/s
+ |
+
+Downlink error rate (aom_container_network_receive_error_packets)
+ |
+Number of error packets received by an NIC per second
+ |
+≥ 0
+ |
+Count/s
+ |
+
+Error packets (aom_container_network_rx_error_packets)
+ |
+Number of error packets received by a measured object
+ |
+≥ 0
+ |
+Count
+ |
+
+Uplink rate (BPS) (aom_container_network_transmit_bytes)
+ |
+Outbound traffic rate of a measured object
+ |
+≥ 0
+ |
+Byte/s
+ |
+
+Uplink error rate (aom_container_network_transmit_error_packets)
+ |
+Number of error packets sent by an NIC per second
+ |
+≥ 0
+ |
+Count/s
+ |
+
+Uplink rate (PPS) (aom_container_network_transmit_packets)
+ |
+Number of data packets sent by an NIC per second
+ |
+≥ 0
+ |
+Packet/s
+ |
+
+Status (aom_process_status)
+ |
+Docker container status
+ |
+0 or 1
+
+ |
+N/A
+ |
+
+Working set memory usage (aom_container_memory_workingset_usage)
+ |
+Usage of the working set memory
+ |
+0–100
+ |
+%
+ |
+
+Used working set memory (aom_container_memory_workingset_used_megabytes)
+ |
+Sum of resident set size (RSS) memory and cache
+ |
+≥ 0
+ |
+MB
+ |
+
+
+
+
+
+
Table 2 Dimensions of container metricsDimension
+ |
+Description
+ |
+
|---|
+
+appID
+ |
+Service ID
+ |
+
+appName
+ |
+Service name
+ |
+
+clusterId
+ |
+Cluster ID
+ |
+
+clusterName
+ |
+Cluster name
+ |
+
+containerID
+ |
+Container ID
+ |
+
+containerName
+ |
+Container name
+ |
+
+deploymentName
+ |
+Kubernetes deployment name
+ |
+
+kind
+ |
+Application type
+ |
+
+nameSpace
+ |
+Cluster namespace
+ |
+
+podID
+ |
+Instance ID
+ |
+
+podName
+ |
+Instance name
+ |
+
+serviceID
+ |
+Inventory ID
+ |
+
+gpuID
+ |
+GPU ID
+ |
+
+npuName
+ |
+NPU name
+ |
+
+npuID
+ |
+NPU ID
+ |
+
+
+
+
+
VM Metrics and Dimensions
+In AOM, VMs refer to processes, and VM metrics refer to process metrics.
+
+
Table 1 Process metricsMetric
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+
|---|
+
+Total CPU cores (aom_process_cpu_limit_core)
+ |
+Total number of CPU cores that have been applied for a measured object
+ |
+≥ 1
+ |
+Cores
+ |
+
+Used CPU cores (aom_process_cpu_used_core)
+ |
+Number of CPU cores used by a measured object
+ |
+≥ 0
+ |
+Cores
+ |
+
+CPU usage (aom_process_cpu_usage)
+ |
+CPU usage of a measured object. That is, the percentage of the used CPU cores to the total CPU cores.
+ |
+0–100
+ |
+%
+ |
+
+Handles (aom_process_handle_count)
+ |
+Number of handles used by a measured object
+ |
+≥ 0
+ |
+N/A
+ |
+
+Max. handles (aom_process_max_handle_count)
+ |
+Maximum number of handles used by a measured object
+ |
+≥ 0
+ |
+N/A
+ |
+
+Total physical memory (aom_process_memory_request_megabytes)
+ |
+Total physical memory that has been applied for a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Physical memory usage (aom_process_memory_usage)
+ |
+Percentage of the used physical memory to the total physical memory
+ |
+0–100
+ |
+%
+ |
+
+Used physical memory (aom_process_memory_used_megabytes)
+ |
+Used physical memory of a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+Status (aom_process_status)
+ |
+Process status
+ |
+0 or 1
+
+ |
+N/A
+ |
+
+Threads (aom_process_thread_count)
+ |
+Number of threads used by a measured object
+ |
+≥ 0
+ |
+N/A
+ |
+
+Total virtual memory (aom_process_virtual_memory_total_megabytes)
+ |
+Total virtual memory that has been applied for a measured object
+ |
+≥ 0
+ |
+MB
+ |
+
+
+
+
+
+
Table 2 Dimensions of process metricsDimension
+ |
+Description
+ |
+
|---|
+
+appName
+ |
+Service name
+ |
+
+clusterId
+ |
+Cluster ID
+ |
+
+clusterName
+ |
+Cluster name
+ |
+
+nameSpace
+ |
+Cluster namespace
+ |
+
+processID
+ |
+Process ID
+ |
+
+processName
+ |
+Process name
+ |
+
+serviceID
+ |
+Inventory ID
+ |
+
+aomApplicationName
+ |
+Application name
+ |
+
+aomApplicationID
+ |
+Application ID
+ |
+
+processCmd
+ |
+Process command ID
+ |
+
+
+
+
+
Instance Metrics and Dimensions
+Instance metrics consist of container or process metrics. The dimensions of instance metrics are the same as those of container or process metrics. For details, see Container Metrics and Dimensions and VM Metrics and Dimensions.
+
Permissions
+If you need to assign different permissions to employees in your enterprise to access your AOM resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your AOM resources.
+
With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to specific types of resources. For example, some software developers in your enterprise need to use AOM resources but must not delete them or perform any high-risk operations such as deleting application discovery rules. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using AOM resources.
+
If your account does not need individual IAM users for permissions management, you may skip over this chapter.
+
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
+
AOM Permissions
By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies or roles to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on AOM.
+
AOM is a project-level service deployed and accessed in specific physical regions. To assign AOM permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing AOM, the users need to switch to a region where they have been authorized to use this service.
+
You can grant users permissions by using roles and policies.
+
- Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you also need to assign dependency roles. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant Elastic Cloud Server (ECS) users only the permissions for managing a certain type of ECSs.
+
Table 1 lists all the system permissions supported by AOM.
+
Table 1 System permissions supported by AOMPolicy Name
+ |
+Description
+ |
+Type
+ |
+Depended System Permissions
+ |
+
|---|
+
+AOM Admin
+ |
+Administrator permissions for AOM. Users granted these permissions can operate and use AOM.
+ |
+System-defined policy
+ |
+CCE Administrator, OBS Administrator, and LTS FullAccess
+ |
+
+AOM Viewer
+ |
+Read-only permissions for AOM. Users granted these permissions can only view AOM data.
+ |
+System-defined policy
+ |
+
+
+
+
+
+
Table 2 lists the common operations supported by each system-defined policy of AOM. Please choose proper system-defined policies according to this table.
+
+
Table 2 Common operations supported by each system-defined policy of AOMOperation
+ |
+AOM Admin
+ |
+AOM Viewer
+ |
+
|---|
+
+Creating a threshold rule
+ |
+√
+ |
+x
+ |
+
+Modifying a threshold rule
+ |
+√
+ |
+x
+ |
+
+Deleting a threshold rule
+ |
+√
+ |
+x
+ |
+
+Creating a threshold template
+ |
+√
+ |
+x
+ |
+
+Modifying a threshold template
+ |
+√
+ |
+x
+ |
+
+Deleting a threshold template
+ |
+√
+ |
+x
+ |
+
+Creating a dashboard
+ |
+√
+ |
+x
+ |
+
+Modifying a dashboard
+ |
+√
+ |
+x
+ |
+
+Deleting a dashboard
+ |
+√
+ |
+x
+ |
+
+Creating an application discovery rule
+ |
+√
+ |
+x
+ |
+
+Modifying an application discovery rule
+ |
+√
+ |
+x
+ |
+
+Deleting an application discovery rule
+ |
+√
+ |
+x
+ |
+
+Exporting a monitoring report
+ |
+√
+ |
+√
+ |
+
+Configuring a VM log collection path
+ |
+√
+ |
+x
+ |
+
+Viewing bucket logs
+ |
+√
+ |
+√
+ |
+
+Adding a log dump
+ |
+√
+ |
+x
+ |
+
+Modifying a log dump
+ |
+√
+ |
+x
+ |
+
+Deleting a log dump
+ |
+√
+ |
+x
+ |
+
+Starting periodical dump
+ |
+√
+ |
+x
+ |
+
+Stopping periodical dump
+ |
+√
+ |
+x
+ |
+
+Configuring a delimiter
+ |
+√
+ |
+x
+ |
+
+Installing the ICAgent
+ |
+√
+ |
+√
+ |
+
+Upgrading the ICAgent
+ |
+√
+ |
+x
+ |
+
+Uninstalling the ICAgent
+ |
+√
+ |
+x
+ |
+
+
+
+
+
To use a custom fine-grained policy, log in to IAM as the administrator and select fine-grained permissions of AOM as required. For details about fine-grained permissions of AOM, see Table 3.
+
+
Table 3 Fine-grained permissions of AOMPermission Name
+ |
+Description
+ |
+Dependency
+ |
+Scenario
+ |
+
|---|
+
+aom:alarmRule:create
+ |
+Creating a threshold rule
+ |
+N/A
+ |
+Creating a threshold rule
+ |
+
+aom:alarmRule:set
+ |
+Modifying a threshold rule
+ |
+Modifying a threshold rule
+ |
+
+aom:alarmRule:get
+ |
+Querying threshold rules
+ |
+Querying all threshold rules or a single threshold rule by rule ID
+ |
+
+aom:alarmRule:delete
+ |
+Deleting threshold rules
+ |
+Deleting threshold rules in batches or a single threshold rule by rule ID
+ |
+
+aom:discoveryRule:list
+ |
+Querying application discovery rules
+ |
+Querying existing application discovery rules
+ |
+
+aom:discoveryRule:delete
+ |
+Deleting an application discovery rule
+ |
+Deleting an application discovery rule
+ |
+
+aom:discoveryRule:set
+ |
+Adding an application discovery rule
+ |
+Adding an application discovery rule
+ |
+
+aom:metric:list
+ |
+Querying time series objects
+ |
+Querying time series objects
+ |
+
+aom:metric:list
+ |
+Querying time series data
+ |
+Querying time series data
+ |
+
+aom:metric:get
+ |
+Querying metrics
+ |
+Querying metrics
+ |
+
+aom:metric:get
+ |
+Querying monitoring data
+ |
+Querying monitoring data
+ |
+
+
+
+
+
+
Privacy and Sensitive Information Protection Statement
+All O&M data will be displayed on the AOM console. Therefore, do not upload your privacy or sensitive data to AOM. If necessary, encrypt such data.
+
Collector Deployment
When you manually install the ICAgent on an Elastic Cloud Server (ECS), your AK/SK will be used as an input parameter in the installation command. To prevent privacy leakage, disable historical record collection before installing the ICAgent. After the ICAgent is installed, it will encrypt and store your AK/SK.
+
+
Container Monitoring
For Cloud Container Engine (CCE) container monitoring, the AOM collector (ICAgent) must run as a privileged container. Evaluate the security risks of the privileged container and identify your container service scenarios. For example, for a node that provides services through logical multi-tenant container sharing, use open-source tools such as Prometheus to monitor the services and do not use ICAgent.
+
+
Disk Partition Metrics
+ - If the host type is CCE, you can view disk partition metrics. The supported OSs are CentOS 7.6 and EulerOS 2.5.
- Log in to the CCE node as the root user and run the docker info | grep 'Storage Driver' command to check the Docker storage driver type. If the command output shows driver type Device Mapper, the thin pool metrics can be viewed. Otherwise, the thin pool metrics cannot be viewed.
+
+
+
Table 1 Disk partition metricsMetric
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+
|---|
+
+Thin pool's metadata space usage
+(aom_host_diskpartition_thinpool_metadata_percent)
+ |
+Percentage of the thin pool's used metadata space to the total metadata space on a CCE node
+ |
+0–100
+ |
+%
+ |
+
+Thin pool's data space usage
+(aom_host_diskpartition_thinpool_data_percent)
+ |
+Percentage of the thin pool's used data space to the total data space on a CCE node
+ |
+0–100
+ |
+%
+ |
+
+Thin pool's disk partition space
+(aom_host_diskpartition_total_capacity_megabytes)
+ |
+Total thin pool's disk partition space on a CCE node
+ |
+≥ 0
+ |
+MB
+ |
+
+
+
+
+
+
Service Overview
+
+
+
+
+
diff --git a/docs/aom/umn/aom_06_6001.html b/docs/aom/umn/aom_06_6001.html
deleted file mode 100644
index 066c9432..00000000
--- a/docs/aom/umn/aom_06_6001.html
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- User Guide
-
-
-
-
-
diff --git a/docs/aom/umn/en-us_image_0000001163171568.png b/docs/aom/umn/en-us_image_0000001163171568.png
new file mode 100644
index 00000000..166f145d
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001163171568.png differ
diff --git a/docs/aom/umn/en-us_image_0000001163172426.png b/docs/aom/umn/en-us_image_0000001163172426.png
new file mode 100644
index 00000000..fad36aa1
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001163172426.png differ
diff --git a/docs/aom/umn/en-us_image_0000001163172776.png b/docs/aom/umn/en-us_image_0000001163172776.png
new file mode 100644
index 00000000..fad36aa1
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001163172776.png differ
diff --git a/docs/aom/umn/en-us_image_0000001163172900.png b/docs/aom/umn/en-us_image_0000001163172900.png
new file mode 100644
index 00000000..fad36aa1
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001163172900.png differ
diff --git a/docs/aom/umn/en-us_image_0000001163330328.png b/docs/aom/umn/en-us_image_0000001163330328.png
new file mode 100644
index 00000000..616b4f83
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001163330328.png differ
diff --git a/docs/aom/umn/en-us_image_0000001163348542.png b/docs/aom/umn/en-us_image_0000001163348542.png
new file mode 100644
index 00000000..08c4364b
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001163348542.png differ
diff --git a/docs/aom/umn/en-us_image_0000001163490512.png b/docs/aom/umn/en-us_image_0000001163490512.png
new file mode 100644
index 00000000..ea326a5d
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001163490512.png differ
diff --git a/docs/aom/umn/en-us_image_0000001167553061.png b/docs/aom/umn/en-us_image_0000001167553061.png
new file mode 100644
index 00000000..a5a99fb3
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001167553061.png differ
diff --git a/docs/aom/umn/en-us_image_0297092397.png b/docs/aom/umn/en-us_image_0000001195728488.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297092397.png
rename to docs/aom/umn/en-us_image_0000001195728488.png
diff --git a/docs/aom/umn/en-us_image_0000001199786128.png b/docs/aom/umn/en-us_image_0000001199786128.png
new file mode 100644
index 00000000..62e93a13
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001199786128.png differ
diff --git a/docs/aom/umn/en-us_image_0000001208742219.png b/docs/aom/umn/en-us_image_0000001208742219.png
new file mode 100644
index 00000000..9bcfdcea
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001208742219.png differ
diff --git a/docs/aom/umn/en-us_image_0000001213679034.png b/docs/aom/umn/en-us_image_0000001213679034.png
new file mode 100644
index 00000000..8c7c7b5c
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001213679034.png differ
diff --git a/docs/aom/umn/en-us_image_0000001216318386.png b/docs/aom/umn/en-us_image_0000001216318386.png
new file mode 100644
index 00000000..062aeba8
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001216318386.png differ
diff --git a/docs/aom/umn/en-us_image_0227418531.png b/docs/aom/umn/en-us_image_0000001238513507.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0227418531.png
rename to docs/aom/umn/en-us_image_0000001238513507.png
diff --git a/docs/aom/umn/en-us_image_0297531019.png b/docs/aom/umn/en-us_image_0000001240568411.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297531019.png
rename to docs/aom/umn/en-us_image_0000001240568411.png
diff --git a/docs/aom/umn/en-us_image_0000001242972085.png b/docs/aom/umn/en-us_image_0000001242972085.png
new file mode 100644
index 00000000..f28b99b3
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001242972085.png differ
diff --git a/docs/aom/umn/en-us_image_0000001242972215.png b/docs/aom/umn/en-us_image_0000001242972215.png
new file mode 100644
index 00000000..f28b99b3
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001242972215.png differ
diff --git a/docs/aom/umn/en-us_image_0000001315765116.png b/docs/aom/umn/en-us_image_0000001315765116.png
deleted file mode 100644
index a4c8f5cb..00000000
Binary files a/docs/aom/umn/en-us_image_0000001315765116.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0000001320760778.png b/docs/aom/umn/en-us_image_0000001320760778.png
deleted file mode 100644
index d9633b08..00000000
Binary files a/docs/aom/umn/en-us_image_0000001320760778.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0000001366881660.png b/docs/aom/umn/en-us_image_0000001366881660.png
deleted file mode 100644
index 8710a737..00000000
Binary files a/docs/aom/umn/en-us_image_0000001366881660.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0000001367106940.png b/docs/aom/umn/en-us_image_0000001367106940.png
deleted file mode 100644
index c6a9584c..00000000
Binary files a/docs/aom/umn/en-us_image_0000001367106940.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0000001368935324.png b/docs/aom/umn/en-us_image_0000001368935324.png
deleted file mode 100644
index 6ffdfdbd..00000000
Binary files a/docs/aom/umn/en-us_image_0000001368935324.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0000001410327528.png b/docs/aom/umn/en-us_image_0000001410327528.png
new file mode 100644
index 00000000..7b5ef7f8
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001410327528.png differ
diff --git a/docs/aom/umn/en-us_image_0297092742.png b/docs/aom/umn/en-us_image_0000001410647264.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297092742.png
rename to docs/aom/umn/en-us_image_0000001410647264.png
diff --git a/docs/aom/umn/en-us_image_0000001410881540.png b/docs/aom/umn/en-us_image_0000001410881540.png
new file mode 100644
index 00000000..4055acd8
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001410881540.png differ
diff --git a/docs/aom/umn/en-us_image_0000001410943068.png b/docs/aom/umn/en-us_image_0000001410943068.png
new file mode 100644
index 00000000..a5a51a6f
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001410943068.png differ
diff --git a/docs/aom/umn/en-us_image_0000001410950444.png b/docs/aom/umn/en-us_image_0000001410950444.png
new file mode 100644
index 00000000..b2578fc3
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001410950444.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411006006.png b/docs/aom/umn/en-us_image_0000001411006006.png
new file mode 100644
index 00000000..61f23e12
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411006006.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411102964.png b/docs/aom/umn/en-us_image_0000001411102964.png
new file mode 100644
index 00000000..7aa32a69
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411102964.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411110332.png b/docs/aom/umn/en-us_image_0000001411110332.png
new file mode 100644
index 00000000..b2578fc3
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411110332.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411169790.png b/docs/aom/umn/en-us_image_0000001411169790.png
new file mode 100644
index 00000000..637192d8
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411169790.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411262784.png b/docs/aom/umn/en-us_image_0000001411262784.png
new file mode 100644
index 00000000..40923489
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411262784.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411270156.png b/docs/aom/umn/en-us_image_0000001411270156.png
new file mode 100644
index 00000000..c22b8cf5
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411270156.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411325438.png b/docs/aom/umn/en-us_image_0000001411325438.png
new file mode 100644
index 00000000..baf48d68
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411325438.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411326706.png b/docs/aom/umn/en-us_image_0000001411326706.png
new file mode 100644
index 00000000..60377e47
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411326706.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411328114.png b/docs/aom/umn/en-us_image_0000001411328114.png
new file mode 100644
index 00000000..5ebc0191
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411328114.png differ
diff --git a/docs/aom/umn/en-us_image_0296835591.png b/docs/aom/umn/en-us_image_0000001411422764.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0296835591.png
rename to docs/aom/umn/en-us_image_0000001411422764.png
diff --git a/docs/aom/umn/en-us_image_0000001411429104.png b/docs/aom/umn/en-us_image_0000001411429104.png
new file mode 100644
index 00000000..b07faa59
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411429104.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411430140.png b/docs/aom/umn/en-us_image_0000001411430140.png
new file mode 100644
index 00000000..145f3f5d
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411430140.png differ
diff --git a/docs/aom/umn/en-us_image_0000001411431544.png b/docs/aom/umn/en-us_image_0000001411431544.png
new file mode 100644
index 00000000..b6f89449
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001411431544.png differ
diff --git a/docs/aom/umn/en-us_image_0000001412030430.png b/docs/aom/umn/en-us_image_0000001412030430.png
new file mode 100644
index 00000000..d225ef3f
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001412030430.png differ
diff --git a/docs/aom/umn/en-us_image_0000001412105490.png b/docs/aom/umn/en-us_image_0000001412105490.png
new file mode 100644
index 00000000..3319d836
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001412105490.png differ
diff --git a/docs/aom/umn/en-us_image_0000001412205042.png b/docs/aom/umn/en-us_image_0000001412205042.png
new file mode 100644
index 00000000..c5d32f17
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001412205042.png differ
diff --git a/docs/aom/umn/en-us_image_0000001415472973.png b/docs/aom/umn/en-us_image_0000001415472973.png
deleted file mode 100644
index cada76e4..00000000
Binary files a/docs/aom/umn/en-us_image_0000001415472973.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0000001417721645.png b/docs/aom/umn/en-us_image_0000001417721645.png
deleted file mode 100644
index 09e580e6..00000000
Binary files a/docs/aom/umn/en-us_image_0000001417721645.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0000001417801529.png b/docs/aom/umn/en-us_image_0000001417801529.png
deleted file mode 100644
index c9c56cf7..00000000
Binary files a/docs/aom/umn/en-us_image_0000001417801529.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0000001420570268.png b/docs/aom/umn/en-us_image_0000001420570268.png
new file mode 100644
index 00000000..57e5625a
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001420570268.png differ
diff --git a/docs/aom/umn/en-us_image_0000001423571610.png b/docs/aom/umn/en-us_image_0000001423571610.png
new file mode 100644
index 00000000..1cf19ab6
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001423571610.png differ
diff --git a/docs/aom/umn/en-us_image_0000001429259356.png b/docs/aom/umn/en-us_image_0000001429259356.png
new file mode 100644
index 00000000..97798589
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001429259356.png differ
diff --git a/docs/aom/umn/en-us_image_0000001459663365.png b/docs/aom/umn/en-us_image_0000001459663365.png
new file mode 100644
index 00000000..45584321
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001459663365.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461046213.png b/docs/aom/umn/en-us_image_0000001461046213.png
new file mode 100644
index 00000000..266f8475
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461046213.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461164845.png b/docs/aom/umn/en-us_image_0000001461164845.png
new file mode 100644
index 00000000..99aa0f01
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461164845.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461193229.png b/docs/aom/umn/en-us_image_0000001461193229.png
new file mode 100644
index 00000000..f4ada410
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461193229.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461281269.png b/docs/aom/umn/en-us_image_0000001461281269.png
new file mode 100644
index 00000000..fa6ebeb4
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461281269.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461287489.png b/docs/aom/umn/en-us_image_0000001461287489.png
new file mode 100644
index 00000000..fcf76802
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461287489.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461410609.png b/docs/aom/umn/en-us_image_0000001461410609.png
new file mode 100644
index 00000000..fd12e250
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461410609.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461502857.png b/docs/aom/umn/en-us_image_0000001461502857.png
new file mode 100644
index 00000000..e89acdeb
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461502857.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461509173.png b/docs/aom/umn/en-us_image_0000001461509173.png
new file mode 100644
index 00000000..9216526a
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461509173.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461509265.png b/docs/aom/umn/en-us_image_0000001461509265.png
new file mode 100644
index 00000000..d7eba0e7
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461509265.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461510225.png b/docs/aom/umn/en-us_image_0000001461510225.png
new file mode 100644
index 00000000..a600bef8
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461510225.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461515217.png b/docs/aom/umn/en-us_image_0000001461515217.png
new file mode 100644
index 00000000..dda1d48b
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461515217.png differ
diff --git a/docs/aom/umn/en-us_image_0297183818.png b/docs/aom/umn/en-us_image_0000001461515245.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297183818.png
rename to docs/aom/umn/en-us_image_0000001461515245.png
diff --git a/docs/aom/umn/en-us_image_0000001461628997.png b/docs/aom/umn/en-us_image_0000001461628997.png
new file mode 100644
index 00000000..9216526a
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461628997.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461631457.png b/docs/aom/umn/en-us_image_0000001461631457.png
new file mode 100644
index 00000000..1b75fbd2
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461631457.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461635045.png b/docs/aom/umn/en-us_image_0000001461635045.png
new file mode 100644
index 00000000..0a16febf
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461635045.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461822513.png b/docs/aom/umn/en-us_image_0000001461822513.png
new file mode 100644
index 00000000..594e91a6
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461822513.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461829877.png b/docs/aom/umn/en-us_image_0000001461829877.png
new file mode 100644
index 00000000..a600bef8
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461829877.png differ
diff --git a/docs/aom/umn/en-us_image_0297092728.png b/docs/aom/umn/en-us_image_0000001461829881.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297092728.png
rename to docs/aom/umn/en-us_image_0000001461829881.png
diff --git a/docs/aom/umn/en-us_image_0000001461862497.png b/docs/aom/umn/en-us_image_0000001461862497.png
new file mode 100644
index 00000000..eb1552a8
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461862497.png differ
diff --git a/docs/aom/umn/en-us_image_0000001461868817.png b/docs/aom/umn/en-us_image_0000001461868817.png
new file mode 100644
index 00000000..0c2420f0
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001461868817.png differ
diff --git a/docs/aom/umn/en-us_image_0000001462420845.png b/docs/aom/umn/en-us_image_0000001462420845.png
new file mode 100644
index 00000000..60af041a
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001462420845.png differ
diff --git a/docs/aom/umn/en-us_image_0000001462529481.png b/docs/aom/umn/en-us_image_0000001462529481.png
new file mode 100644
index 00000000..655a017b
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001462529481.png differ
diff --git a/docs/aom/umn/en-us_image_0000001462784353.png b/docs/aom/umn/en-us_image_0000001462784353.png
new file mode 100644
index 00000000..d4b4a009
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001462784353.png differ
diff --git a/docs/aom/umn/en-us_image_0000001464256522.png b/docs/aom/umn/en-us_image_0000001464256522.png
new file mode 100644
index 00000000..0ac01636
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001464256522.png differ
diff --git a/docs/aom/umn/en-us_image_0000001471047065.png b/docs/aom/umn/en-us_image_0000001471047065.png
new file mode 100644
index 00000000..76978208
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001471047065.png differ
diff --git a/docs/aom/umn/en-us_image_0000001479016049.png b/docs/aom/umn/en-us_image_0000001479016049.png
new file mode 100644
index 00000000..be379c09
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001479016049.png differ
diff --git a/docs/aom/umn/en-us_image_0000001479138361.png b/docs/aom/umn/en-us_image_0000001479138361.png
new file mode 100644
index 00000000..df749c51
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001479138361.png differ
diff --git a/docs/aom/umn/en-us_image_0000001479298177.png b/docs/aom/umn/en-us_image_0000001479298177.png
new file mode 100644
index 00000000..8b4927ef
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001479298177.png differ
diff --git a/docs/aom/umn/en-us_image_0000001367745042.png b/docs/aom/umn/en-us_image_0000001561946430.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0000001367745042.png
rename to docs/aom/umn/en-us_image_0000001561946430.png
diff --git a/docs/aom/umn/en-us_image_0000001562264710.png b/docs/aom/umn/en-us_image_0000001562264710.png
new file mode 100644
index 00000000..145f3f5d
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001562264710.png differ
diff --git a/docs/aom/umn/en-us_image_0000001562424626.png b/docs/aom/umn/en-us_image_0000001562424626.png
new file mode 100644
index 00000000..616b4f83
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001562424626.png differ
diff --git a/docs/aom/umn/en-us_image_0000001582213732.png b/docs/aom/umn/en-us_image_0000001582213732.png
new file mode 100644
index 00000000..4fdf91eb
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001582213732.png differ
diff --git a/docs/aom/umn/en-us_image_0000001598820253.png b/docs/aom/umn/en-us_image_0000001598820253.png
new file mode 100644
index 00000000..b161d58f
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001598820253.png differ
diff --git a/docs/aom/umn/en-us_image_0000001599019641.png b/docs/aom/umn/en-us_image_0000001599019641.png
new file mode 100644
index 00000000..b161d58f
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001599019641.png differ
diff --git a/docs/aom/umn/en-us_image_0000001612744525.png b/docs/aom/umn/en-us_image_0000001612744525.png
new file mode 100644
index 00000000..c22b8cf5
Binary files /dev/null and b/docs/aom/umn/en-us_image_0000001612744525.png differ
diff --git a/docs/aom/umn/en-us_image_0169698516.png b/docs/aom/umn/en-us_image_0169698516.png
deleted file mode 100644
index eff2c8b4..00000000
Binary files a/docs/aom/umn/en-us_image_0169698516.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0201820771.png b/docs/aom/umn/en-us_image_0201820771.png
deleted file mode 100644
index 469287fb..00000000
Binary files a/docs/aom/umn/en-us_image_0201820771.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0227418464.png b/docs/aom/umn/en-us_image_0227418464.png
new file mode 100644
index 00000000..e9b21624
Binary files /dev/null and b/docs/aom/umn/en-us_image_0227418464.png differ
diff --git a/docs/aom/umn/en-us_image_0227418562.png b/docs/aom/umn/en-us_image_0263893495.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0227418562.png
rename to docs/aom/umn/en-us_image_0263893495.png
diff --git a/docs/aom/umn/en-us_image_0263893507.png b/docs/aom/umn/en-us_image_0263893507.png
new file mode 100644
index 00000000..7ed499f4
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263893507.png differ
diff --git a/docs/aom/umn/en-us_image_0297092730.png b/docs/aom/umn/en-us_image_0263893524.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297092730.png
rename to docs/aom/umn/en-us_image_0263893524.png
diff --git a/docs/aom/umn/en-us_image_0297092729.png b/docs/aom/umn/en-us_image_0263893562.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297092729.png
rename to docs/aom/umn/en-us_image_0263893562.png
diff --git a/docs/aom/umn/en-us_image_0297183816.png b/docs/aom/umn/en-us_image_0263893576.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297183816.png
rename to docs/aom/umn/en-us_image_0263893576.png
diff --git a/docs/aom/umn/en-us_image_0263893584.png b/docs/aom/umn/en-us_image_0263893584.png
new file mode 100644
index 00000000..a4a21f56
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263893584.png differ
diff --git a/docs/aom/umn/en-us_image_0297092733.png b/docs/aom/umn/en-us_image_0263893592.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297092733.png
rename to docs/aom/umn/en-us_image_0263893592.png
diff --git a/docs/aom/umn/en-us_image_0296835776.png b/docs/aom/umn/en-us_image_0263893612.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0296835776.png
rename to docs/aom/umn/en-us_image_0263893612.png
diff --git a/docs/aom/umn/en-us_image_0263893614.png b/docs/aom/umn/en-us_image_0263893614.png
new file mode 100644
index 00000000..606d4281
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263893614.png differ
diff --git a/docs/aom/umn/en-us_image_0263893649.png b/docs/aom/umn/en-us_image_0263893649.png
new file mode 100644
index 00000000..a4a21f56
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263893649.png differ
diff --git a/docs/aom/umn/en-us_image_0297092736.png b/docs/aom/umn/en-us_image_0263893650.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297092736.png
rename to docs/aom/umn/en-us_image_0263893650.png
diff --git a/docs/aom/umn/en-us_image_0263893651.png b/docs/aom/umn/en-us_image_0263893651.png
new file mode 100644
index 00000000..87689689
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263893651.png differ
diff --git a/docs/aom/umn/en-us_image_0263893658.png b/docs/aom/umn/en-us_image_0263893658.png
new file mode 100644
index 00000000..e1371a33
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263893658.png differ
diff --git a/docs/aom/umn/en-us_image_0297183813.png b/docs/aom/umn/en-us_image_0263893660.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297183813.png
rename to docs/aom/umn/en-us_image_0263893660.png
diff --git a/docs/aom/umn/en-us_image_0263893663.png b/docs/aom/umn/en-us_image_0263893663.png
new file mode 100644
index 00000000..87689689
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263893663.png differ
diff --git a/docs/aom/umn/en-us_image_0263897677.png b/docs/aom/umn/en-us_image_0263897677.png
new file mode 100644
index 00000000..cc695a1b
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263897677.png differ
diff --git a/docs/aom/umn/en-us_image_0263897681.png b/docs/aom/umn/en-us_image_0263897681.png
new file mode 100644
index 00000000..c15eaa6a
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263897681.png differ
diff --git a/docs/aom/umn/en-us_image_0263897772.png b/docs/aom/umn/en-us_image_0263897772.png
new file mode 100644
index 00000000..9d30c78a
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263897772.png differ
diff --git a/docs/aom/umn/en-us_image_0263897774.png b/docs/aom/umn/en-us_image_0263897774.png
new file mode 100644
index 00000000..570dd9f8
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263897774.png differ
diff --git a/docs/aom/umn/en-us_image_0263897780.png b/docs/aom/umn/en-us_image_0263897780.png
new file mode 100644
index 00000000..b6ecb94c
Binary files /dev/null and b/docs/aom/umn/en-us_image_0263897780.png differ
diff --git a/docs/aom/umn/en-us_image_0201820799.png b/docs/aom/umn/en-us_image_0269669234.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0201820799.png
rename to docs/aom/umn/en-us_image_0269669234.png
diff --git a/docs/aom/umn/en-us_image_0201820725.png b/docs/aom/umn/en-us_image_0269669235.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0201820725.png
rename to docs/aom/umn/en-us_image_0269669235.png
diff --git a/docs/aom/umn/en-us_image_0297092402.png b/docs/aom/umn/en-us_image_0269669237.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297092402.png
rename to docs/aom/umn/en-us_image_0269669237.png
diff --git a/docs/aom/umn/en-us_image_0297092403.png b/docs/aom/umn/en-us_image_0269669238.png
similarity index 100%
rename from docs/aom/umn/en-us_image_0297092403.png
rename to docs/aom/umn/en-us_image_0269669238.png
diff --git a/docs/aom/umn/en-us_image_0269669240.png b/docs/aom/umn/en-us_image_0269669240.png
new file mode 100644
index 00000000..4a8b69dd
Binary files /dev/null and b/docs/aom/umn/en-us_image_0269669240.png differ
diff --git a/docs/aom/umn/en-us_image_0269669241.png b/docs/aom/umn/en-us_image_0269669241.png
new file mode 100644
index 00000000..4112a44e
Binary files /dev/null and b/docs/aom/umn/en-us_image_0269669241.png differ
diff --git a/docs/aom/umn/en-us_image_0270729777.png b/docs/aom/umn/en-us_image_0270729777.png
new file mode 100644
index 00000000..c752f2b4
Binary files /dev/null and b/docs/aom/umn/en-us_image_0270729777.png differ
diff --git a/docs/aom/umn/en-us_image_0296834237.png b/docs/aom/umn/en-us_image_0296834237.png
deleted file mode 100644
index d15548db..00000000
Binary files a/docs/aom/umn/en-us_image_0296834237.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0296834240.png b/docs/aom/umn/en-us_image_0296834240.png
deleted file mode 100644
index ce28b477..00000000
Binary files a/docs/aom/umn/en-us_image_0296834240.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0296834241.png b/docs/aom/umn/en-us_image_0296834241.png
deleted file mode 100644
index a6ff5c1f..00000000
Binary files a/docs/aom/umn/en-us_image_0296834241.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297078492.png b/docs/aom/umn/en-us_image_0297078492.png
deleted file mode 100644
index 28d164ff..00000000
Binary files a/docs/aom/umn/en-us_image_0297078492.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297078493.png b/docs/aom/umn/en-us_image_0297078493.png
deleted file mode 100644
index 66c17988..00000000
Binary files a/docs/aom/umn/en-us_image_0297078493.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297078494.png b/docs/aom/umn/en-us_image_0297078494.png
deleted file mode 100644
index cf360d90..00000000
Binary files a/docs/aom/umn/en-us_image_0297078494.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297078495.png b/docs/aom/umn/en-us_image_0297078495.png
deleted file mode 100644
index f021720d..00000000
Binary files a/docs/aom/umn/en-us_image_0297078495.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297078496.png b/docs/aom/umn/en-us_image_0297078496.png
deleted file mode 100644
index 75e4680b..00000000
Binary files a/docs/aom/umn/en-us_image_0297078496.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092398.png b/docs/aom/umn/en-us_image_0297092398.png
deleted file mode 100644
index 42efe224..00000000
Binary files a/docs/aom/umn/en-us_image_0297092398.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092399.png b/docs/aom/umn/en-us_image_0297092399.png
deleted file mode 100644
index 469287fb..00000000
Binary files a/docs/aom/umn/en-us_image_0297092399.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092400.png b/docs/aom/umn/en-us_image_0297092400.png
deleted file mode 100644
index eb539ad8..00000000
Binary files a/docs/aom/umn/en-us_image_0297092400.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092401.png b/docs/aom/umn/en-us_image_0297092401.png
deleted file mode 100644
index 09e580e6..00000000
Binary files a/docs/aom/umn/en-us_image_0297092401.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092404.png b/docs/aom/umn/en-us_image_0297092404.png
deleted file mode 100644
index 5d634c8d..00000000
Binary files a/docs/aom/umn/en-us_image_0297092404.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092725.png b/docs/aom/umn/en-us_image_0297092725.png
deleted file mode 100644
index e459f10c..00000000
Binary files a/docs/aom/umn/en-us_image_0297092725.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092726.png b/docs/aom/umn/en-us_image_0297092726.png
deleted file mode 100644
index 36f8b530..00000000
Binary files a/docs/aom/umn/en-us_image_0297092726.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092727.png b/docs/aom/umn/en-us_image_0297092727.png
deleted file mode 100644
index 307b7444..00000000
Binary files a/docs/aom/umn/en-us_image_0297092727.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092731.png b/docs/aom/umn/en-us_image_0297092731.png
deleted file mode 100644
index f08f0b7d..00000000
Binary files a/docs/aom/umn/en-us_image_0297092731.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092732.png b/docs/aom/umn/en-us_image_0297092732.png
deleted file mode 100644
index 3297b01f..00000000
Binary files a/docs/aom/umn/en-us_image_0297092732.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092734.png b/docs/aom/umn/en-us_image_0297092734.png
deleted file mode 100644
index 53ff1b29..00000000
Binary files a/docs/aom/umn/en-us_image_0297092734.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092735.png b/docs/aom/umn/en-us_image_0297092735.png
deleted file mode 100644
index d002cf6b..00000000
Binary files a/docs/aom/umn/en-us_image_0297092735.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092737.png b/docs/aom/umn/en-us_image_0297092737.png
deleted file mode 100644
index f08f0b7d..00000000
Binary files a/docs/aom/umn/en-us_image_0297092737.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092738.png b/docs/aom/umn/en-us_image_0297092738.png
deleted file mode 100644
index 3297b01f..00000000
Binary files a/docs/aom/umn/en-us_image_0297092738.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092739.png b/docs/aom/umn/en-us_image_0297092739.png
deleted file mode 100644
index 53ff1b29..00000000
Binary files a/docs/aom/umn/en-us_image_0297092739.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092740.png b/docs/aom/umn/en-us_image_0297092740.png
deleted file mode 100644
index 53ff1b29..00000000
Binary files a/docs/aom/umn/en-us_image_0297092740.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297092743.png b/docs/aom/umn/en-us_image_0297092743.png
deleted file mode 100644
index 3340fd4e..00000000
Binary files a/docs/aom/umn/en-us_image_0297092743.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297106347.png b/docs/aom/umn/en-us_image_0297106347.png
deleted file mode 100644
index c0a75de5..00000000
Binary files a/docs/aom/umn/en-us_image_0297106347.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180622.png b/docs/aom/umn/en-us_image_0297180622.png
deleted file mode 100644
index e12acf60..00000000
Binary files a/docs/aom/umn/en-us_image_0297180622.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180623.png b/docs/aom/umn/en-us_image_0297180623.png
deleted file mode 100644
index 2e3a405c..00000000
Binary files a/docs/aom/umn/en-us_image_0297180623.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180624.png b/docs/aom/umn/en-us_image_0297180624.png
deleted file mode 100644
index 3be7998f..00000000
Binary files a/docs/aom/umn/en-us_image_0297180624.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180645.png b/docs/aom/umn/en-us_image_0297180645.png
deleted file mode 100644
index 598fc62e..00000000
Binary files a/docs/aom/umn/en-us_image_0297180645.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180646.png b/docs/aom/umn/en-us_image_0297180646.png
deleted file mode 100644
index 515e7b1e..00000000
Binary files a/docs/aom/umn/en-us_image_0297180646.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180648.png b/docs/aom/umn/en-us_image_0297180648.png
deleted file mode 100644
index 39de4d6c..00000000
Binary files a/docs/aom/umn/en-us_image_0297180648.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180649.png b/docs/aom/umn/en-us_image_0297180649.png
deleted file mode 100644
index e9f20c58..00000000
Binary files a/docs/aom/umn/en-us_image_0297180649.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180650.png b/docs/aom/umn/en-us_image_0297180650.png
deleted file mode 100644
index 9719c1aa..00000000
Binary files a/docs/aom/umn/en-us_image_0297180650.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180651.png b/docs/aom/umn/en-us_image_0297180651.png
deleted file mode 100644
index e38c1dab..00000000
Binary files a/docs/aom/umn/en-us_image_0297180651.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180661.png b/docs/aom/umn/en-us_image_0297180661.png
deleted file mode 100644
index df6b645c..00000000
Binary files a/docs/aom/umn/en-us_image_0297180661.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180662.png b/docs/aom/umn/en-us_image_0297180662.png
deleted file mode 100644
index 661effc0..00000000
Binary files a/docs/aom/umn/en-us_image_0297180662.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180663.png b/docs/aom/umn/en-us_image_0297180663.png
deleted file mode 100644
index 3d97a0d1..00000000
Binary files a/docs/aom/umn/en-us_image_0297180663.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297180664.png b/docs/aom/umn/en-us_image_0297180664.png
deleted file mode 100644
index cbb6f3a0..00000000
Binary files a/docs/aom/umn/en-us_image_0297180664.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297183034.png b/docs/aom/umn/en-us_image_0297183034.png
deleted file mode 100644
index fc638e93..00000000
Binary files a/docs/aom/umn/en-us_image_0297183034.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297183036.png b/docs/aom/umn/en-us_image_0297183036.png
deleted file mode 100644
index d13bf789..00000000
Binary files a/docs/aom/umn/en-us_image_0297183036.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297183037.png b/docs/aom/umn/en-us_image_0297183037.png
deleted file mode 100644
index 75729a66..00000000
Binary files a/docs/aom/umn/en-us_image_0297183037.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297183038.png b/docs/aom/umn/en-us_image_0297183038.png
deleted file mode 100644
index 3365ecc6..00000000
Binary files a/docs/aom/umn/en-us_image_0297183038.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297183045.png b/docs/aom/umn/en-us_image_0297183045.png
deleted file mode 100644
index 9765c0ae..00000000
Binary files a/docs/aom/umn/en-us_image_0297183045.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297183060.png b/docs/aom/umn/en-us_image_0297183060.png
deleted file mode 100644
index 73fd9fe7..00000000
Binary files a/docs/aom/umn/en-us_image_0297183060.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297183061.png b/docs/aom/umn/en-us_image_0297183061.png
deleted file mode 100644
index 4c3fcb12..00000000
Binary files a/docs/aom/umn/en-us_image_0297183061.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297183062.png b/docs/aom/umn/en-us_image_0297183062.png
deleted file mode 100644
index 421be688..00000000
Binary files a/docs/aom/umn/en-us_image_0297183062.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297183817.png b/docs/aom/umn/en-us_image_0297183817.png
deleted file mode 100644
index fde0fb6e..00000000
Binary files a/docs/aom/umn/en-us_image_0297183817.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297194004.png b/docs/aom/umn/en-us_image_0297194004.png
deleted file mode 100644
index 598fc62e..00000000
Binary files a/docs/aom/umn/en-us_image_0297194004.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297531017.png b/docs/aom/umn/en-us_image_0297531017.png
deleted file mode 100644
index a567d7cb..00000000
Binary files a/docs/aom/umn/en-us_image_0297531017.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297531020.png b/docs/aom/umn/en-us_image_0297531020.png
deleted file mode 100644
index fde0fb6e..00000000
Binary files a/docs/aom/umn/en-us_image_0297531020.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297531022.png b/docs/aom/umn/en-us_image_0297531022.png
deleted file mode 100644
index 81ff2f58..00000000
Binary files a/docs/aom/umn/en-us_image_0297531022.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297531023.png b/docs/aom/umn/en-us_image_0297531023.png
deleted file mode 100644
index 62c4d35f..00000000
Binary files a/docs/aom/umn/en-us_image_0297531023.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297610957.png b/docs/aom/umn/en-us_image_0297610957.png
deleted file mode 100644
index 9ca5c4eb..00000000
Binary files a/docs/aom/umn/en-us_image_0297610957.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297616583.png b/docs/aom/umn/en-us_image_0297616583.png
deleted file mode 100644
index 07a38127..00000000
Binary files a/docs/aom/umn/en-us_image_0297616583.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297616584.png b/docs/aom/umn/en-us_image_0297616584.png
deleted file mode 100644
index 722c8441..00000000
Binary files a/docs/aom/umn/en-us_image_0297616584.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297616606.png b/docs/aom/umn/en-us_image_0297616606.png
deleted file mode 100644
index c488d73f..00000000
Binary files a/docs/aom/umn/en-us_image_0297616606.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297616607.png b/docs/aom/umn/en-us_image_0297616607.png
deleted file mode 100644
index 14447a66..00000000
Binary files a/docs/aom/umn/en-us_image_0297616607.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297616608.png b/docs/aom/umn/en-us_image_0297616608.png
deleted file mode 100644
index 5d634c8d..00000000
Binary files a/docs/aom/umn/en-us_image_0297616608.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297616609.png b/docs/aom/umn/en-us_image_0297616609.png
deleted file mode 100644
index e459f10c..00000000
Binary files a/docs/aom/umn/en-us_image_0297616609.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297616611.png b/docs/aom/umn/en-us_image_0297616611.png
deleted file mode 100644
index 36f8b530..00000000
Binary files a/docs/aom/umn/en-us_image_0297616611.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_image_0297616613.png b/docs/aom/umn/en-us_image_0297616613.png
deleted file mode 100644
index 285a6685..00000000
Binary files a/docs/aom/umn/en-us_image_0297616613.png and /dev/null differ
diff --git a/docs/aom/umn/en-us_topic_0296826282.html b/docs/aom/umn/en-us_topic_0296826282.html
deleted file mode 100644
index 21eeedb1..00000000
--- a/docs/aom/umn/en-us_topic_0296826282.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-Process of Using AOM
-Process of Using AOM shows the process of using AOM.
-
Figure 1 Process of using AOM
-
- (Mandatory) Register an account.
- (Mandatory) Create a cloud host.
- (Mandatory) Install the ICAgent.
ICAgent is the data collector of AOM. It runs on hosts to collect metrics, logs, and application performance data in real time. Ensure that you have installed the ICAgent before using AOM.
- - The system automatically discovers services.
After the ICAgent is installed, the services that meet the built-in service discovery rules on the host will be automatically discovered.
- - (Optional) Configure a log collection path.
To view the logs of the monitored host, you must first configure a log collection path. The ICAgent then will collect host logs from the configured path and display them on AOM.
- - (Optional) Perform O&M.
You can use AOM functions such as dashboard, monitoring, alarm reporting, and log management to implement routine O&M.
-
-
