Mention a specific handler in an alert notification group
Configure Cloud Monitor 2.0 so that each alert notification delivered to a DingTalk group, Lark group, or WeCom group @-mentions the O&M engineer who must respond to it. This tutorial connects an IM robot, a contact, a notification policy, and a per-engineer phone binding to make the mention link work end to end.
Prerequisites
Cloud Monitor 2.0 is activated and a workspace is created.
A DingTalk group, Lark group, or WeCom group is created to receive alert notifications.
The O&M engineers who handle the alerts are members of the notification group.
A custom robot is added in the group settings of DingTalk, Lark, or WeCom, so that its webhook address is available for Step 1.
Considerations
Review the following requirements before you start. The @-mention takes effect only when all of them are met.
Phone number consistency — The Phone value on the contact created in Step 2 must be identical to the number that the O&M engineer binds in Step 4.
Both robot and contact required — The notification policy in Step 3 must include both the IM robot from Step 1 and a contact (or contact group or on-call schedule) from Step 2. A policy that references only the robot delivers the message without an @-mention.
Contact activation required — A newly created contact must complete verification through the activation link. Until activation completes, the contact cannot receive notifications.
Firewall whitelist — Notifications sent by an IM robot do not require firewall whitelist configuration.
Step 1: Create an IM robot
Register an IM robot in Cloud Monitor 2.0 that points at the custom robot already added to the DingTalk, Lark, or WeCom group.
Log on to the Cloud Monitor 2.0 console and select the target workspace.
Click Alert Center, and then choose Notify Management > Notify Object.
Click the IM bot tab, and then click Create IM bot.
In the dialog box, configure the following parameters.
Parameter
Description
Name
A custom robot name. Duplicate names are allowed.
Identifier
A custom identifier. It cannot be the same as the identifier of an existing robot. If you leave this parameter blank, the system generates an identifier automatically.
Type
Select DingTalk, Lark, or WeCom to match the group that receives the notifications.
URL
The webhook address of the custom robot in the group. Obtain this address from the group settings of DingTalk, Lark, or WeCom after you add the custom robot.
Signing secret
The signature secret of the robot. You can set a signature secret for a robot in a DingTalk group or a Lark group.
Language
The language of alert notification messages. Chinese and English are supported.
Step 2: Create the notification recipient
Decide which recipient form matches how the alerts are staffed, and then create it in Cloud Monitor 2.0.
Scenario | Recipient form to create |
One O&M engineer handles the alerts | A single contact (the default path) |
Several O&M engineers share the same alerts around the clock | A contact group that contains every relevant contact |
Several O&M engineers rotate on shifts | An on-call schedule that references the relevant contacts |
Create the contact
Every recipient form starts with at least one contact, so create the contact first.
Log on to the Cloud Monitor 2.0 console and select the target workspace.
Click Alert Center, and then choose Notify Management > Notify Object.
On the Contact tab, click Create a contact.
In the dialog box, configure the following parameters.
Parameter
Description
Name
A custom contact name. Duplicate names are allowed.
Identifier
A custom identifier. It cannot be the same as the identifier of an existing contact. If you leave this parameter blank, the system generates an identifier automatically.
Language
The language of alert notification messages. Chinese and English are supported.
Phone
The mobile phone number that receives alerts. This number must be identical to the phone number that the O&M engineer binds in Step 4.
E-mail
The email address that receives alert notifications.
IM user ID (required)
The messaging-platform identifier of the O&M engineer: the user ID in DingTalk or Lark, or the account in WeCom.
After you receive the activation link at the phone number and email address that you entered, click the link to complete the verification. Until the contact is activated, it cannot receive notifications.
(Optional) Create a contact group
Create a contact group when several O&M engineers share the same alerts and each notification must mention all of them.
On the Contact tab, click the Contact group list, and then click Create a contact group.
In the dialog box, enter a name and an identifier, select the contacts to include, and then click OK.
(Optional) Use an on-call schedule
Use an on-call schedule when several O&M engineers rotate on shifts and each notification must mention only the contact who is on duty at the time the alert fires.
Step 3: Configure the notification policy
Bind the IM robot from Step 1 and the recipient from Step 2 in a notification policy, and confirm that the policy uses @-mention as the notification method.
Log on to the Cloud Monitor 2.0 console and select the target workspace.
Click Alert Center, and then choose Notify Management > Notify Strategy.
Create a notification policy or edit an existing one.
On the Notification config page, set the notification recipients:
In the Notification objects section, select the IM robot that you created in Step 1 for the first drop-down list.
Select the contact, contact group, or on-call schedule that you created in Step 2 for the second drop-down list.
For the Contact, Contact Group, and On-call Schedule recipient types, confirm that the notification method is @ in group. The Alert Center selects @ in group by default.
Step 4: Bind each O&M engineer's phone number
Each O&M engineer to be mentioned performs this step personally, after the group has received at least one alert notification. Notify every engineer who is registered as a contact to complete the binding for their own account.
When the alert notification group receives an alert notification, click any link in the alert card.
In the phone number binding panel that appears, follow the instructions to bind your phone number. The number must be identical to the Phone value recorded on your contact in Step 2.
Enter the verification code that you receive, and then click OK.