When an alert fires, Application Real-Time Monitoring Service (ARMS) Alert Management can @mention specific contacts in a DingTalk, Lark, or WeCom group chat. This directs notifications to the responsible person so they can respond immediately, rather than relying on everyone in the chat to manually check each alert.
How it works
ARMS delivers @mentions through three connected components:
Chatbot -- delivers alert messages to the group chat.
Contact -- maps a person's identity (phone number or user ID) so ARMS can resolve the @mention.
Notification policy -- connects the chatbot and contacts, controlling when and how alerts are routed.
Each platform resolves @mentions using a different identity type:
| Platform | Identity type | Where to find it |
|---|---|---|
| DingTalk | Mobile phone number | The mobile phone number specified in the contact record |
| WeCom | User ID | Console > Enterprise Management > Members and Departments Management > click the employee > user ID (requires admin permissions) |
| Lark | User ID | Enterprise Management > Members and Departments > click the employee > user ID (requires admin permissions) |
Prerequisites
Before you begin, make sure that you have:
A DingTalk, Lark, or WeCom group chat that receives alert notifications
The alert-handling personnel as members of the group chat
Create a chatbot
Create a chatbot in the ARMS console for the target group chat. For setup instructions, see:
Create contacts
Log on to the ARMS console. In the left-side navigation pane, choose Alert Management > Notification Objects.
On the Contacts tab, click Create Contact.
In the Create Contact dialog box, enter a contact name and a mobile phone number, then verify the phone number.
NoteThis phone number must match the one bound in the final step (Bind a mobile phone number).
(WeCom and Lark only) Add user IDs. DingTalk does not require user IDs.
WeCom: Log on to the WeCom app. Choose Console > Enterprise Management > Members and Departments Management, click the employee, and configure the user ID.
Lark: In the navigation pane, choose Enterprise Management > Members and Departments, click the employee, and configure the user ID.
Admin permissions are required for both platforms.
Set other parameters as needed and click OK.
Add a contact group (optional)
To @mention multiple contacts when an alert fires, add them to the same contact group.
On the Contact tab, click Create Contact Group.
In the Create Contact Group dialog box, specify the Group Name, select the contacts, and click OK.
When an alert fires, all contacts in the group are @mentioned.
Create a schedule (optional)
To route alerts to the on-duty contact based on shift hours, create a scheduling policy. When an alert fires, the on-duty contact is @mentioned.
For instructions, see Create a scheduling policy.
Configure a notification policy
A notification policy connects the chatbot and contacts, telling ARMS where to deliver alerts and who to @mention.
Log on to the ARMS console. In the left-side navigation pane, choose Alert Management > Notification Policies.
On the Notification Policies page, create a notification policy or edit an existing one.
In the Notification Objects step, add notification objects:
Click Add Notification Object and select the chatbot you created.
Click Add Notification Object and select the contact, contact group, or schedule.
NoteThe @mentions option is selected by default.
Configure remaining parameters as needed. For details, see Create and manage a notification policy.
Bind a mobile phone number
Each contact must bind their phone number through the group chat so ARMS can resolve @mentions.
Wait for the group chat to receive an alert notification, then click a link in the alert card.
In the Bind Mobile Phone Number dialog box, enter the phone number. This must be the same number specified during contact creation.
Enter the verification code and click OK.
After binding, the contact is @mentioned automatically when an alert is triggered.