DocsICP FilingConsole
官方文档
首页

Notification objects

更新时间：
复制 MD 格式
产品详情
我的收藏

Notification objects define who receives an alert notification and how. You can send notifications to contacts through phone calls, text messages, and email, or integrate with chatbots and custom webhooks. This helps you effectively manage on-call schedules and ensure that alerts reach the right people.

Access the feature

  1. Log in to the Cloud Monitor console.

  2. In the left-side navigation pane, choose Alert Center or choose All Features > Alert Center.

  3. On the Alert Center page, choose Notification Management > Notification objects.

Phone, SMS, and email notifications

Contacts

  1. On the Contacts tab, click Create Contact.

  2. In the Create Contact dialog box, configure the following parameters and click OK.

    • Name: Enter a name for the contact. This name does not need to be unique.

    • Identifier: Enter a custom identifier. The identifier must be unique among all contacts.

    • Language: Select the language for alert notifications. You can choose Chinese or English.

    • Phone: Enter the phone number to receive alerts.

    • E-mail: Enter the email address to receive alerts.

  3. Click the activation link sent to your phone number and email address to complete the verification.

  4. After creating a contact, you can find, edit, or delete it on the Contacts tab:

    • To search for a contact, enter a keyword from the contact name in the search box on the right and click the 搜索 icon.

    • To edit a contact, find the contact, click Edit in the Actions column, modify the information in the dialog box that appears, and then click OK.

    • To delete a single contact, find the contact, click Delete in the Actions column, and then click OK in the confirmation message.

    • To delete multiple contacts, select the contacts to delete, click Delete at the bottom of the list, and then click OK.

Contact groups

  1. On the Contacts tab, click Contact group list.

  2. Click Create Contact Group.

  3. In the Create Contact Group dialog box, configure the following parameters and click OK.

    • Name: Enter a name for the contact group.

    • Identifier: Enter a unique identifier for the contact group.

    • Contacts: Select existing contacts to add to the group.

  4. After you create a contact group, you can find, edit, or delete it on the Contact group list tab:

    • To search for a contact group, enter a keyword from the contact group name in the search box on the right and click the 搜索 icon.

    • To edit or delete a contact group, find the group and click Edit or Delete in the Actions column.

Important

  • Before you delete a contact or contact group, ensure no notification policy uses it. Otherwise, alert notifications may fail to be sent.

  • You can only delete contacts and contact groups you created.

Chatbot notifications

  1. On the Notification objects page, click the chatbots tab, and then click Create Chatbot.

  2. In the Create Chatbot dialog box, configure the following parameters and click OK.

    • Name: Enter a name for the chatbot. This name does not need to be unique.

    • Identifier: Enter a unique identifier for the chatbot. The identifier must be unique among all chatbots.

    • Type: Select the chatbot type. Supported types include DingTalk, Lark, Slack, WeCom, and Teams.

    • URL: Enter the callback URL for the chatbot.

    • Language: Select the language for alert notifications. You can choose Chinese or English.

  3. After you create a chatbot, you can find, edit, or delete it on the chatbots tab:

    • To search for a chatbot, select a type from the Please select a type dropdown list and enter a keyword in the Name search box.

    • To edit a chatbot, find the chatbot, click Edit in the Actions column, modify the information in the Edit Chatbot dialog box, and click Confirm.

    • To delete a chatbot, find the chatbot and click Delete in the Actions column. To delete multiple chatbots, select the ones to delete, click Delete at the bottom of the list, and then click OK.

Note

  • Chatbot notifications (DingTalk, Lark, WeCom, Slack, and Teams) do not require a firewall allowlist.

  • Cloud Monitor retries failed alert notifications up to three times, with a 5-second timeout per request and no backoff between retries.

Custom webhook notifications

  1. On the Notification objects page, click the custom webhook tab, and then click Create Webhook.

  2. In the Create Webhook dialog box, configure the following parameters and click Confirm.

    • Name: Enter a name for the webhook. This name does not need to be unique.

    • Identifier: Enter a unique identifier for the webhook. The identifier must be unique among all webhooks.

    • URL: Enter the callback URL for the custom webhook.

    • Headers: Set the header parameters. Enter them as <key><value> pairs. You can set up to five parameters.

    • Method: Select the request method, either GET or POST.

    • Data Format: Select the data format, either FORM or JSON.

    • Language: Select the language for alert notifications, either Chinese or English.

  3. After you create a custom webhook, you can find, edit, or delete it on the custom webhook tab:

    • To search for a custom webhook, enter a keyword in the Name search box.

    • To edit a custom webhook, find the webhook, click Edit in the Actions column, modify the information in the Edit Webhook dialog box, and then click Confirm.

    • To delete a custom webhook, find the webhook and click Delete in the Actions column. To delete multiple webhooks, select the ones you want to delete, click Batch delete at the bottom of the list, and then click Confirm.

Note

  • Cloud Monitor sends alert notifications to your URL as HTTP or HTTPS POST requests. Add the following IP address ranges to your firewall allowlist:

    106.11.225.0/24
106.11.226.0/24
106.11.227.0/24
106.11.242.0/24
106.11.167.0/24
106.11.245.0/24
59.82.0.0/16
59.82.84.0/24
203.119.128.0/17
203.119.156.0/24
121.41.9.246

  • Cloud Monitor retries failed alert callbacks up to three times, with a 5-second timeout per request and no backoff between retries.

Webhook payload fields

Category

Field

Type

Description

CloudEvents standard fields

specversion

String

The CloudEvents specification version.

id

String

The unique ID of the event.

type

String

The event type, such as "ALERT" or "Change".

subtype

String

The event subtype, such as "NORMAL_TRIGGER" (triggered) or "NORMAL_RESOLVE" (resolved).

source

String

The event source path, in the format /{userId}/rules/{ruleId}.

sourcetype

String

The identifier for the event source system, such as "ALERT_ALIYUN_ALERT_CENTER".

time

String

The time the event occurred, in ISO 8601 format.

timestamp

Long

The Unix timestamp of the event, in milliseconds.

subject

String

The name of the alert rule.

datacontenttype

String

The content type of the data field. The value is fixed to "application/json".

Core alert fields

severity

String

The severity of the alert, such as CRITICAL, WARNING, or INFO.

status

String

The alert status, such as "OCCURRED" (triggered) or "RESOLVED" (resolved).

userId

String

The user ID.

ruleId

String

The ID of the alert rule.

workspace

String

The workspace identifier. For example, the default workspace in a region is default-cms-{userId}-{region}.

traceId

String

The trace ID, used for troubleshooting.

alertMessage

String

A summary of the alert.

alertEntityId

String

The unique identifier of the alert entity.

resource object

resource.entity.domain

String

The domain of the entity, such as "ecs", "rds", or "apm".

resource.entity.entity_type

String

The type of the entity, such as "instance" or "disk".

resource.entity.entity_id

String

The ID of the entity.

resource.entity.prop

Object

The properties of the entity, in key-value pairs, such as instanceName.

resource.tags

Object

The resource tags, in key-value pairs, including instanceId and regionId.

labels object

labels._cms_region

String

The region ID, such as "cn-hangzhou".

labels._cms_workspace

String

The workspace identifier.

labels._cms_rule_id

String

The ID of the alert rule.

labels._cms_rule_name

String

The name of the alert rule.

annotations object

annotations.current_value

String

The current value of the metric.

annotations._cms_promql

String

The PromQL query expression that triggered the alert.

annotations._cms_business_url

String

The URL of the business details page.

annotations._cms_alert_rule_url

String

The URL of the alert rule configuration page.

annotations._cms_alert_history_url

String

The URL of the alert history page.

data object

data.value

Number

The metric value that triggered the alert.

data.threshold

Number

The alert threshold.

data.comparisonOperator

String

The comparison operator.

alertEntityFields object

alertEntityFields

Object

The flattened key properties of the alert entity, such as instanceName and regionId.

Quick link fields

ruleUrl

String

The URL of the alert rule in the console.

entityUrl

String

The URL of the alert entity details page in the console.

alertRuleUrl

String

The URL of the alert rule configuration page.

alertHistoryUrl

String

The URL of the alert history page.

Previous：Escalation and silence policiesNext：Action integration