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.
- 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.
- Dimensions of system metrics cannot be changed. Different types of metrics have different dimensions. For more information, see Network Metrics and Dimensions to Service Metrics and Dimensions.
The dimensions listed in Network Metrics and Dimensions to Service Metrics and Dimensions are the dimensions of metrics collected and reported by the AOM backend. You can select these dimensions when calling APIs. Resources are filtered and displayed by dimensions on the AOM frontend.
- Dimensions of custom metrics must be 1 to 32 characters long, which need to be customized.