Application Real-Time Monitoring Service:Getting Started

Step 1: Integrate monitored services

In this example, ARMS alerts are integrated. ARMS alerts are integrated with the Alert Management sub-service by default. For more information about how to integrate other monitored services with the Alert Management sub-service, see Overview.

Step 2: Create a notification object

The Alert Management sub-service allows you to send alert notifications to notification objects via SMS, phone call, email, or DingTalk. In this section, a DingTalk group chat is created to describe how to configure a DingTalk chatbot in Alert Management and send alert notifications to the group chat. For information about how to create other notification objects, see Overview.

1. Create a custom chatbot in the DingTalk group that you created in your DingTalk client and obtain the webhook URL of the chatbot. For more information, see Obtain the webhook URL of a DingTalk chatbot.
2. Log on to the ARMS console.
3. In the left-side navigation pane, choose Alert Management > Notification Objects.
4. On the Notification Objects page, click the DingTalk/Lark/WeCom tab. Then, click DingTalk.
5. In the Create DingTalk Chatbot panel, configure the parameters and click OK. The following table describes the parameters.

   Parameter	Description
   Name	Specify a name for the DingTalk chatbot.
   Signature Key	Optional. If you specify a signature key, DingTalk authentication is performed by using the signature key. If you do not specify a signature key, a whitelist is used for authentication by default. The keyword of the whitelist is Alert.
   Chatbot Webhook URL	Enter the webhook URL of the DingTalk chatbot.
   Whether DingTalk Chatbot Sends Daily Statistics	If you select this option, you must enter the points in time at which the daily statistics are sent. Separate multiple points in time with commas (,). Specify the points in time in the HH:SS format. The information that ARMS sends at the specified points in time includes the total number of alerts generated on the current day, the number of resolved alerts, and the number of alerts to be resolved.
   Card Content Configuration	Customize the style and content of the alert notification card.

Step 3: Create notification policies

This example shows how to merge alert events with severity level P1 into one alert notification and send it to the DingTalk group chat. For more information, see the Create and manage a notification policy section in this topic.

1. Log on to the ARMS console. In the left-side navigation pane, choose Alert Management > Notification Policies.
2. In the upper-right corner of the Notification Policies page, click Create Notification Policy.
3. On the Create Notification Policy page, enter a notification policy name.

4. In the Matching Rule step, configure a matching rule for alert events.

   Important

   Silence policies take precedence over notification policies. Alert events that match a silence policy are silenced and cannot be matched by a notification policy.

   1. Select No Preset Source. The notification policy filters all alert events based on the matching rule and sends alert notifications.

   2. Specify one or more expressions. You can add custom tags or select existing tags. For example, _aliyun_arms_alert_level equals P1.

   3. Click Next.

5. In the Event Grouping step, select Do Not Group, and then click Next.

6. In the Notification Objects section, configure the following parameters.

   1. Set the Notification Objects parameter to DingTalk/Lark/WeCom and select the DingTalk chatbot that you created in Step 2.

   2. Specify whether to send clearing notifications after an alert is cleared.

      Specify whether the status of an alert automatically changes to Resolved if all events related to the alert change to the Restored state. If an alert is cleared, the system sends clearing notifications to the alert handler.

   3. Specify a notification template. For more information, see Configure a notification template and a webhook template.

   4. Configure the time period during which alert notifications are sent. For example, you can set the Notification Period parameter to 00:00-23:59.

   5. Optional:Select the ticket system to which alert notifications are sent. For more information, see Overview.

   6. Click Next.

7. In the Repeat Notifications & Escalation Policy step, specify whether to send repeat notifications or use an escalation policy.

   • If you use an escalation policy, alert notifications are sent only once till an alert is cleared.

   • If you want to send repeat notifications, configure an interval at which two alert notifications are sent. Alert notifications are continuously sent at the specified interval till an alert is cleared.

   • If you use an escalation policy, alert notifications are sent to other notification objects based on the escalation policy till an alert is cleared.

8. Click Save.

Step 4: Create event rules

Different methods are used to create alert rules in different sub-services.

• For more information about how to manage an alert rule in Application Monitoring, see Create and manage an alert rule in Application Monitoring (new).

• Create an alert rule in Browser Monitoring. For more information, see Create and manage a Browser Monitoring alert rule.

• Create an alert rule in Prometheus Service. For more information, see Create an alert rule.

Step 5: View and manage alert cards

Alert cards in DingTalk group chats display basic information about alerts. You can modify the display content of alert cards by editing alert notification templates in notification policies. For more information, see the Manage alerts in a notification group section in this topic.