All Products
Search
Document Center

Application Real-Time Monitoring Service:Integrate Cloud Monitor alerts

Last Updated:Jun 20, 2026

Learn how to integrate alerts from Cloud Monitor into Alert Management in Application Real-Time Monitoring Service (ARMS).

Background

Alert Management in ARMS supports using a webhook to ingest alerts generated by Cloud Monitor. After you integrate the alerts, you can manage them in a central location. This centralizes alert configurations that are otherwise scattered across systems with different handling capabilities.

You can integrate Cloud Monitor with Alert Management in ARMS in two ways:

Create a Cloud Monitor integration

  1. Log on to the ARMS console. In the left-side navigation pane, choose Alert Management > Integrations.

  2. On the Alert Integration tab, click CloudMonitor.

  3. In the Create Cloud Monitor Integration dialog box, enter a name and description for the integration, and specify the auto-recovery time for alert events.

    Note

    Automatic recovery time after timeout: If an alert event is not triggered again within the specified period of time, the alert event is automatically cleared.

  4. In the Products Enabling Alert Events section, the All Products area displays the products that are supported by Cloud Monitor and can be integrated into Alert Management. Select the products for which you want to integrate alerts, click the right_arrow icon, and then click Save.

    Note

    This feature automatically traverses all alert rules configured for the selected products and changes the callback URL of these rules to https://alerts.aliyuncs.com/api/v1/cm/callback/{{token}}. In the URL, {{token}} is the key that is automatically generated when the integration is created.

    After you complete the configuration, the new Cloud Monitor integration appears on the Alert Integration tab. The integration list shows the name, integration URL (including the automatically generated key), type, and creation time for the integration. Its status is Enabled and its activity level is Ready. In the Actions column, you can Edit, Delete, or Disable the integration.

Integrate a specific Cloud Monitor alert rule

Important

You can only integrate specific alert rules into an existing Cloud Monitor integration.

  1. On the Integration page, go to the Alert Integration tab and copy the integration URL of the target Cloud Monitor integration.

  2. Log on to the Cloud Monitor console.

  3. In the left-side navigation pane, choose Alerts > Alert Rules.

  4. On the Alert Rules page, find the alert rule that you want to modify and click Modify in the Actions column.

  5. In the Advanced Settings section, set the alert callback URL to the copied integration URL.

  6. Click Confirm.

Edit an integration

Alert Management in ARMS provides preset mappings between Cloud Monitor alert source fields and ARMS alert fields. You can also add or modify field mappings on the Edit Integration page as needed.

  1. On the Alert Integration tab, find the integration that you want to manage and click Edit in the Actions column.

  2. In the Event Mapping section, click Send Test Data.

  3. In the Send Test Data dialog box, enter the alert content of a third-party alert source in the JSON format and click Send.

    Note
    • If the message Uploaded. No events are generated. Configure mappings based on the original data. appears, the fields of the alert source are not mapped to the fields of ARMS alert events. The data that is sent is displayed in the left-side box. This allows you to select the source fields when you configure mappings.

    • If the message Uploaded. appears, the alert content is reported to the Alert Event History page. For more information, see View alert event history.

  4. In the Send Test Data dialog box, click Disable.

  5. In the left part of the Event Mapping section, click the data records for which you want to configure mappings to view the details.

  6. In the right part of the Event Mapping section, configure the mappings between the alert source fields and the ARMS alert fields.

    1. Optional:In the Select Root Node section, specify whether to enable batch processing.

      If an array node exists in the alert data, you can specify the array node as the root node. The data that belongs to the root node is processed in batches.

      After you select Use Batch Processing, select the array node to be batch processed as the root node.

      Note

      If multiple array nodes exist in the alert data, you can select only one of the array nodes for batch processing.

    2. In the Map Source Fields to Target Fields section, map the fields of the alert source to the alert fields of ARMS.

      Click the mapping icon to change the method for field mapping.

      • Direct: The specified field of the alert source is directly mapped to the specified alert field of ARMS.

      • Series: You can use delimiters to concatenate multiple fields of the alert source into one field, and then map this field to the specified alert field of ARMS. Only special characters can be used as delimiters.

      • Conditional: The specified alert source fields are mapped to the ARMS alert fields only when the field values meet the specified conditions.

      • Mapping table: The alert source severity is mapped to the ARMS alert severity. The mapping table contains only the severity field.

      The following table describes the alert fields of ARMS.

      Alert field

      Description

      alertname

      The name of the custom alert.

      severity

      The severity level of the alert. You must configure mappings for this field. The mapping method must be set to Direct.

      message

      The description of the alert. The description is used as the content of the alert message. The description cannot exceed 15,000 characters in length.

      value

      The sample value of a metric.

      imageUrl

      The URL of the line chart that contains Grafana metrics. The URL is used to map the line chart.

      check

      The check item of the alert. Examples: CPU, JVM, Application Crash, and Deployment.

      source

      The source of the alert.

      class

      The type of the object that triggers the alert event, for example, host.

      service

      The source service of the alert. Example: Login Service.

      startat

      The timestamp that represents the start time of the event.

      endat

      The timestamp that represents the end time of the event.

      generatorUrl

      The URL of the event details.

  7. Configure field deduplication for alert events.

    To reduce duplicate data, the system uses relevant fields as the basis for deduplication. ARMS Alert Management allows you to preview the deduplication grouping results of historical event data that is displayed in the Event Mapping section. You can change the fields to be deduplicated.

    Note

    You can configure deduplication only for events that are not cleared.

    1. In the Event Deduplication section on the Integration Details page, select the fields that are used for deduplication.

      If multiple events have the same value for a specified field, the events are merged into one alert notification.

    2. Click Deduplication Test to preview the alert group after deduplication.

      Note

      The deduplication test takes effect only on the latest 10 data records that are uploaded in the left part of the Event Mapping section.

  8. After you configure the settings, click Save.

View the details about an alert event

  1. In the left-side navigation pane of the ARMS console, choose Alert Management > Alert Event History.

  2. On the Alert Event History page, click the name of the alert event to view the event details. For more information, see View alert event history.

Add products

To add alerts for new products to an existing Cloud Monitor integration:

  1. In the ARMS console, find the target Cloud Monitor integration on the Integration page and choose More > Select Service.

  2. In the dialog box that appears, select the Cloud Monitor services to ingest alerts from, click the right_arrow icon, and then click Save.

Manage integrations

In the left-side navigation pane, choose Alert Management > Integrations. On the Alert Integration tab, you can perform the following operations on the integrations that you created:

  • View the details of an integration: Find the integration and then click the row. On the Integration Details page, view the integration details.

  • Update a key: Find the target integration, choose More > Update Key in the Actions column, and then click Confirm.

    Important

    After you update the key, you must re-add the Cloud Monitor products. For more information, see Add products.

  • Modify an integration: Find the integration and then click Edit in the Actions column. On the Integration Details page, modify the integration information and then click Save.

  • Enable or disable an integration: Find the integration and then click Disable or Enable in the Actions column.

  • Delete an integration: Find the integration and then click Delete in the Actions column. In the message that appears, click OK.

  • Add an event processing flow to an integration: Find the integration and click Add Event Processing Flow in the Actions column. For more information, see Event processing flow.

  • Create a notification policy: Find the integration for which you want to create a notification policy, and click More in the Actions column. In the list that appears, click Create Notification Policy. For more information, see Notification policies.

What to do next

After you create a notification policy, the system generates alerts and sends alert notifications for reported alert events based on the notification policy that you created. For more information, see Notification policies. On the Alert Sending History page, you can view the alerts that are generated based on the configured notification policy. For more information, see View alert sending history.