Application Real-Time Monitoring Service (ARMS) allows you to create notification policies and specify matching rules for alert events. If a matching rule is triggered, alert notifications are sent to the contacts by using the specified notification methods. This way, the contacts can resolve issues at the earliest opportunity.
PrerequisitesContacts are created. For more information, see Overview.
Create a notification policy
- Log on to the ARMS console. In the left-side navigation pane, choose .
- In the upper-right corner of the Notification Policies page, click Create Notification Policy.
- On the Create Notification Policy page, enter a notification policy name.
- In the Matching Rule step, configure a matching rule for alert events.
- Select a data source.
- If you specify a source of alert events, ARMS processes alert events of the specified data source and sends alert notifications based on the matching rule that you configured.
- If you select No Preset Source, ARMS processes all alert events and sends alert notifications based on the matching rule that you configured.
- Specify one or more expressions. You can add custom tags or select existing tags.
Existing tags include:
- The fields that are included in an alert rule expression. For information about how to create a tag for an alert rule in Alibaba Cloud Prometheus Service, see Create an alert rule for a Prometheus instance.
- The default tags that are provided by ARMS. The following table describes the default tags.
Category Tag Description Common fields alertname The name of the alert. clustername The name of the Kubernetes cluster. severity The severity level of the alert. Valid values:
namespace The name of the namespace. For more information, see Namespaces in Kubernetes documentation. pod_name The name of the Pod. For more information, see Pods in Kubernetes documentation. Preset system fields _aliyun_arms_integration_name The name of the integration that you specified as the data source. By default, ARMS returns the integration name ARMS-DEFAULT. _aliyun_arms_involvedObject_id The ID of the object that triggers the alert. _aliyun_arms_involvedObject_name The name of the object that triggers the alert. _aliyun_arms_region_id The region ID of ARMS. _aliyun_arms_alert_rule_id The ID of the alert rule. _aliyun_arms_alert_type The type of the alert rule. Valid values:
- 101: Prometheus Service alert
- 5: Application Monitoring alert
- 4: Browser Monitoring alert
- If you want an alert to be triggered when multiple conditions are met at the same time, click + condition to add a matching condition in the same matching rule.
- If you want an alert to be triggered when one condition is met, click + add rule to add a matching rule.
- Click Next.
- Select a data source.
- In the Event Grouping step, select an option to specify whether to group alert events, and click Next.
- If you specify that alert events are not grouped, all alert events are sent to the contacts in an alert notification.
- If you specify that alert events are grouped, you must also specify a field. Alert events that have the same field value are grouped. Each group of alert events is sent to contacts in one alert notification.
- In the Notification Objects step, configure the following parameters.
- Click + Add Notification Object to select contacts. Contact types:
- Contact: When you select a contact, select a notification method, such as by phone call, text message, or email.
- Contact group: When you select a contact group, select a notification method, such as by phone call, text message, or email.
- Shift: When you select a shift, select a notification method, such as by phone call, text message, or email.
- Instant messaging (IM) applications: You can send alert notifications to contacts from IM applications, including DingTalk, Lark, and WeCom.
- Webhook: You can use a webhook to send alert notifications.
- Specify whether to send clearing notifications after an alert is cleared. If you choose to send clearing notifications after an alert is cleared, the status of an alert automatically changes to Resolved if all events related to the alert are handled. When an alert is cleared, the system sends clearing notifications to the contacts.
- Specify a notification template. For more information, see Configure a notification template and a webhook template.
- Specify the period of time during which alert notifications are sent.
- Optional:Select the ticket system to which alert notifications are sent. For more information, see Notification integrations.
- Click Next.
- Click + Add Notification Object to select contacts.
- In the Repeat Notifications & Escalation Policy step, specify whether to send repeat notifications or use an escalation policy.
- If you do not use repeat notifications or an escalation policy, the alert notification is sent only once before an alert is cleared.
- If you want to send repeat notifications, specify an interval at which two alert notifications are sent. Alert notifications are continuously sent at the specified interval until the alert is cleared.
- If you use an escalation policy, alert notifications are sent to other notification objects based on the escalation policy until the alert is cleared.
- Click Save.
Manage the notification policy
After you create a notification policy, the policy is displayed on the Notification Policies page. You can perform the following operations to manage notification policies on this page:
- Modify a notification policy: Find the notification policy that you want to modify. Click the name of the notification policy or click Edit in the Actions column. After you modify the notification policy, click Save.
- Enable or disable a notification policy: Turn on or turn off the Status switch.
- Delete a notification policy: Find the notification policy that you want to delete, and click Delete in the Actions column. In the message that appears, click OK.
- Duplicate a notification policy: Find the notification policy that you want to duplicate, and click Copy in the Actions column.