Cloud Monitor:Monitor an Alibaba Cloud service

Procedure

1. Log on to the Cloud Monitor 2.0 console, and select a workspace. In the left navigation pane, click Integration Center.

2. On the Integration Center page, search for and click ApsaraDB RDS. Then, set parameters as described in the following table.

   Parameter	Description
   Region	The region of the current workspace. This parameter is unmodifiable.
   Policy Name	Default: The system automatically generates a policy name. Custom: Click Custom to specify a custom policy name.
   Scope	All Entities: Integrates all entities in the current region, including existing and future entities. By Resource Group: Integrates all entities in the specified resource group. By Tag: Filters entities to integrate based on tags. When Managed Service for Prometheus integrates cloud service metrics through Hybrid Cloud Monitoring, it adds instance metadata, such as the instance ID or instance tags, as labels to the metrics. This enriches the metrics beyond the original Cloud Monitor tags. You can either use the default common labels or add custom instance tags as labels. For more information, see Tag description. Manual Selection: Manually select the entities to integrate.

   Note

   • Managed Service for Prometheus uses Hybrid Cloud Monitoring to retrieve cloud service monitoring data. Because of this dependency, if Hybrid Cloud Monitoring is not activated for your account, you are prompted to activate it. Click Activate Now to open the activation page. For more information, see Activate Hybrid Cloud Monitoring. After the activation is complete, click Re-detect to continue integrating the monitoring data for ApsaraDB RDS for MySQL.

   • Activating Hybrid Cloud Monitoring is an asynchronous operation. If the status remains inactive after re-detection, wait 10 to 20 seconds and click Re-detect again.

3. Click OK. The integration takes about one to two minutes to complete.

Procedure

1. Log on to the Cloud Monitor 2.0 console, and select a workspace. In the left navigation pane, click Integration Center.

2. On the Integration Center page, search for and click ApsaraDB RDS. Then, set parameters as described in the following table.

   Parameter	Description
   Region	The region of the current workspace. This parameter is unmodifiable.
   Policy Name	Default: The system automatically generates a policy name. Custom: Click Custom to specify a custom policy name.
   Scope	All Entities: Integrates all entities in the current region, including existing and future entities. By Resource Group: Integrates all entities in the specified resource group. By Tag: Filters entities to integrate based on tags. When Managed Service for Prometheus integrates cloud service metrics through Hybrid Cloud Monitoring, it adds instance metadata, such as the instance ID or instance tags, as labels to the metrics. This enriches the metrics beyond the original Cloud Monitor tags. You can either use the default common labels or add custom instance tags as labels. For more information, see Tag description. Manual Selection: Manually select the entities to integrate.

   Note

   • Managed Service for Prometheus uses Hybrid Cloud Monitoring to retrieve cloud service monitoring data. Because of this dependency, if Hybrid Cloud Monitoring is not activated for your account, you are prompted to activate it. Click Activate Now to open the activation page. For more information, see Activate Hybrid Cloud Monitoring. After the activation is complete, click Re-detect to continue integrating the monitoring data for ApsaraDB RDS for MySQL.

   • Activating Hybrid Cloud Monitoring is an asynchronous operation. If the status remains inactive after re-detection, wait 10 to 20 seconds and click Re-detect again.

3. Click OK. The integration takes about one to two minutes to complete.

Tag description

When Managed Service for Prometheus integrates cloud service metrics using Hybrid Cloud Monitoring, it adds instance metadata, such as the instance ID and instance tags, as labels to the metrics. This process enriches the metrics beyond the original tags from Cloud Monitor. You can use the default common labels or add custom instance tags as labels.

• Default common tags

  The specific tags vary depending on the cloud product. During metric collection, Managed Service for Prometheus attaches other relevant instance metadata as tags to the corresponding metrics.

  Tag	Description
  id	The instance ID.
  instanceName	The instance name.
  resourceGroupId	The resource group ID.
  resourceGroupName	The resource group name.
  regionId	The region of the instance.
  zoneId	The zone.
  userId	The ID of the Alibaba Cloud account.
  namespace	The ID of the integration environment.
  product	The cloud product to which the instance belongs.
  measure	The corresponding metric name in Cloud Monitor.
  measure_desc	The corresponding metric description in Cloud Monitor.

• Custom tags

  Tags on a cloud product instance with the o11y.aliyun.dev/ prefix are also included in the metric data. For example, if an instance has the tag o11y.aliyun.dev/project=abc, a new tag project=abc is added to the metrics.