Integrating cloud service metrics with Managed Service for Prometheus

更新时间:
复制 MD 格式

Alibaba Cloud Managed Service for Prometheus supports the integration of metrics from multiple cloud services. The metrics come from two main sources: Cloud Monitor, and advanced metrics that are collected directly from cloud products by Alibaba Cloud Managed Service for Prometheus.

Cloud Monitor metrics

For a list of metrics supported by Cloud Monitor, see Metrics for cloud services. All cloud service metrics can theoretically be integrated into Managed Service for Prometheus. If the cloud service that you want to integrate is not available in the Integration Center, you can submit a ticket.

For Managed Service for Prometheus agent versions V1.1.32(v5.1-e0c90c68) and later, metrics from integrated cloud products are automatically aligned with Cloud Monitor metrics. This means that new metrics reported to Cloud Monitor by a cloud product are automatically ingested into Managed Service for Prometheus without requiring additional configuration. After ingestion, the metric names are automatically prefixed with Aliyun${ProductName}_ to prevent naming conflicts between different cloud products. For example, after the CPUUtilization metric of Elastic Compute Service (ECS) is ingested into Managed Service for Prometheus, the corresponding metric name is AliyunEcs_CPUUtilization. When Cloud Monitor metrics are ingested into Prometheus, metrics for the cloud service instance are ingested from all regions.

Note

After you integrate a cloud service with Managed Service for Prometheus, you may find that new metrics for the service appear in Cloud Monitor but cannot be found in Prometheus. If this issue occurs, log on to the ARMS console. Go to the Integration Management > Integrated Environments > Cloud Service Region Environment page and enter the corresponding environment. On the Agent Settings tab, check whether the agent version is V1.1.32 or later. If the agent version meets this requirement, go to the Component Management page. Then, find the corresponding component and check whether it is the latest version. If it is not, upgrade the component.

Conversion rules for Cloud Monitor metrics integrated into Prometheus

Metric names are converted to the following format: Aliyun${ProductName}_${MetricName}

  • ${MetricName}: Special characters in the original Cloud Monitor metric name (any character other than letters, numbers, and underscores) are replaced with underscores (_).

  • ${ProductName} standard rules: The product name is derived from the namespace of the cloud service metric according to the following rules.

    • Remove the acs_ prefix.

    • Remove the _dashboard suffix.

    • Remove the underscores (_).

    • Capitalize the first letter of the product name abbreviation and convert the rest to lowercase.

    ${ProductName} special rules: For historical reasons, some cloud services use custom ProductName values. The following table lists these exceptions.

    Namespace

    Product category

    Product name

    acs_cc

    cc_iot

    Cciot

    acs_newbgpddos

    newbgpddos

    ddos-pro

    acs_bandwidth_package

    sharebandwidthpackages

    Ebwp

    acs_vpc_eip

    eip

    Eip, Vpceip

    acs_elasticsearch

    elasticsearch

    Es, Elasticsearch

    acs_elasticsearch

    logstash

    Logstash

    acs_global_acceleration

    acs_global_acceleration, globalaccelerationplus

    Ga

    acs_hbaseserverless

    hbaseserverless

    Hbase, Hbaseserverless

    acs_nat_gateway

    nat_gateway, enhanced_nat_gateway, nat_bandwithpackage

    Nat, Natgateway

    acs_pai_dlc

    dlc

    Paidlc

    acs_pai_dsw

    dsw

    Paidsw

    acs_pai_quota

    quota

    Paiquota

    acs_kvstore

    kvstore_sharding, kvstore_splitrw, kvstore_standard, kvstore_old

    Redis, Kvstore

    waf

    waf, hybrid_waf, wafv3, hybrid_wafv3

    Waf

    acs_kafka

    kafkaV3, kafka

    AliKafka

    acs_amqp

    amqp_instance

    Amqp_instance

    acs_disk

    disk_replica_pair_async, dbsc, disk, disk_replica_group_async

    Dbsc, Disk

    acs_disk

    disk_replica_pair_async, dbsc, disk, disk_replica_group_async

    Dbsc

    acs_gws

    gws

    Ecd

    acs_emr

    emr, emr_serverless_starrocks, emr_workflow

    Starrock, Emr

    acs_fnf

    functionflow

    Functionflow

    acs_hybriddb

    gpdb

    Gpdb

    acs_hologres

    hologres_follower

    Hologres_follower

    acs_hologres

    hologres_shared

    Hologres_shared

    acs_hologres

    hologres_standard

    Hologres_standard

    acs_hologres

    hologres_warehouse

    Hologres_warehouse

    acs_hitsdb

    influxdb, tsdb

    Influxdb

    acs_ipv6_bandwidth

    ipv6gateway_gw

    Gw

    acs_learn

    learn_eas

    Learn_eas

    acs_learn

    learn_eas_resource

    Pai_learn_eas_resource

    acs_maxcompute_prepay

    maxcompute_common

    Maxcompute_common

    acs_maxcompute_prepay

    maxcompute_subscription

    Maxcompute_subscription

    acs_maxcompute_prepay

    maxcompute_tunnel_subscription

    Maxcompute_tunnel_subscription

    acs_mongodb

    mongodb_replicaset

    Mongodb_replicaset

    acs_mongodb

    mongodb_replicaset

    Mongodb_replicaset

    acs_mongodb

    mongodb_singlenode

    Mongodb_singlenode

    acs_rds_dashboard

    rds

    Rds

    acs_rds_dashboard

    rds_cluster

    Rds, Rds_cluster

    acs_rds_dashboard

    postgresql

    Rds

    acs_rds_dashboard

    sqlserver

    Rds, Sqlserver

    acs_rocketmq

    rocketmq

    Rocketmq5

    acs_physical_connection

    port, vbr

    Port, Vbr

Advanced metrics

Managed Service for Prometheus collects advanced metrics directly from cloud services. These metrics are more detailed and have shorter collection intervals. Currently, only some products support advanced metrics. Unlike Cloud Monitor metrics, the integration of advanced metrics does not support instances across all regions, and the default integration policy varies by product. The original names of advanced metrics are retained and not renamed during integration.

The following cloud services support advanced metric integration:

Cloud service

Integration policy

MSE

By default, metrics are integrated only for cloud service instances in the same region as the selected data storage region.

ACK

Metrics are integrated per cluster.

ASK

Metrics are integrated per cluster.

ACS

Metrics are integrated per cluster.

ACK One

Metrics are integrated per cluster.

Realtime Compute for Apache Flink

Metrics are integrated per workspace.

Lindorm

By default, metrics are integrated only for cloud service instances in the same region as the selected data storage region.

ApsaraMQ for Confluent

By default, metrics are integrated only for cloud service instances in the same region as the selected data storage region.

ApsaraMQ for Kafka

By default, metrics are integrated only for cloud service instances in the same region as the selected data storage region.

ApsaraMQ for RocketMQ (5.0)

By default, metrics are integrated only for cloud service instances in the same region as the selected data storage region.

ASM

By default, metrics are integrated only for cloud service instances in the same region as the selected data storage region.

PAI-EAS

By default, metrics are integrated only for cloud service instances in the same region as the selected data storage region.

Intelligent Computing Lingjun

By default, metrics are integrated only for cloud service instances in the same region as the selected data storage region.

Storage policy

When cloud service metrics are integrated with Managed Service for Prometheus, a Prometheus instance is automatically created for storage. For more information about storage policies, see Data storage description.