Application Real-Time Monitoring Service (ARMS) allows you to create notification policies and specify dispatch conditions for alert events. If a dispatch condition is met, the system sends alert notifications to the specified contacts by using the specified notification methods. This way, the contacts can resolve issues at the earliest opportunity.

Prerequisites

One or more contacts are created. For more information, see Overview.

Create a notification policy

  1. Log on to the ARMS console.
  2. In the left-side navigation pane, choose Alert Management > Notification Policies.
  3. On the Notification policies page, click Create Notification Policy.
  4. On the right side of the page, enter a name for the notification policy in the Name field.
  5. In the Match Alert Event Rules section, perform the following steps:
    1. Specify a source of alert events or select No Preset Source.
      • If you specify a source of alert events, ARMS processes alert events of the specified source and sends alert notifications based on the dispatch conditions that you configure.
      • If you select No Preset Source, ARMS processes all alert events and sends alert notifications based on the dispatch conditions that you configure.
    2. Configure one or more dispatch conditions. You can use a custom field or select an existing field. For example, you can specify the following condition: alertname is equal to Memory Usage.

      The existing fields are divided into the following three types:

      • The fields that are included in an alert rule expression.
      • The fields that you create in an alert rule in Prometheus Service. For more information, see Create an alert rule for a Prometheus instance.
      • The default fields that are provided by ARMS. The following table describes the default fields.
        Type Field Description
        Common field alertname The name of the alert.
        clustername The name of the cluster.
        severity The severity of the alert.
        namespace The name of the namespace. For more information, see Kubernetes documentation.
        pod_name The name of the Pod. For more information, see Kubernetes documentation.
        System preset field _aliyun_arms_integration_name The name of the integration. By default, ARMS reports 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 ID of the region.
        _aliyun_arms_alert_rule_id The ID of the alert rule.
        _aliyun_arms_alert_type The type of the alert. Valid values:
        • 101: Prometheus Service alert
        • 5: Application Monitoring alert
        • 4: Browser Monitoring alert
      Note
      • If you want an alert to be triggered only when multiple conditions are met, click + condition to add more conditions.
      • If you want an alert to be triggered when one of the specified alert rules is met, click + Add Rule to add more alert rules.
      Assignment rules
  6. In the Event Handling section, configure the following parameters.
    Dispatch-event handling
    Note For information about the intelligent denoising feature, see Configure the intelligent denoising feature.
    Parameter Description
    Processing Method
    • Generate Alerts: Alerts are triggered and sent to contacts when alert events are detected.
    • Do Not Generate Alerts (Drop Events): Alerts are not triggered when alert events are detected.
    Note If you create two notification policies that use the same settings except the Processing Method parameter, the notification policy whose Processing Method parameter is set to Do Not Generate Alerts (Drop Events) has a higher priority than the notification policy whose Processing Method parameter is set to Generate Alerts. In this case, alert notifications are not sent to contacts when alert events are detected.
    Advanced Settings
    Event Group
    • Do Not Group: All alerts are sent to the contacts in a notification.
    • Specifies that events with the same field content are assigned to a group: You can select fields to group alert events. Alerts with the same field are sent to the contacts in a notification.
    Automatic Alert Recovery Specifies whether the status of an alert automatically changes to Resolved when all events related to the alert change to the Restored state. ARMS notifies contacts when the alert status changes to Resolved.
  7. In the When an alert is generated section, configure the following parameters.
    Notification policy - When an alert is generated
    Parameter Description
    Contacts You can specify one or more contacts, contact groups, instant messaging (IM) robot, or schedules.
    Notification Methods Select the method that is used to send alert notifications. Valid values: DingTalk, Mail, SMS, Phone, and WebHook. You can select one or more notification methods. If you want to use an IM robot to send alert notifications, you do not need to specify the Notification Method parameter.
    Note
    • If you want to notify a contact by phone, you must first verify the phone number of the contact. For more information, see Verify a phone number.
    • You can create custom notification templates. Click Notification template. In the Notification Template dialog box, configure templates for notifications that are sent via email, SMS, or phone.
    Notification period The period during which repeated alert notifications are sent.
    Method to Escalate Notifications The method that is used to remind contacts to handle alerts that remain unresolved for an extended period of time. Valid values:
    • Recurring Notifications: If you select Recurring Notifications, you must specify the interval at which alert notifications are sent. ARMS sends alert notifications at the specified interval during the specified time period before the alerts are resolved.
    • Escalation Policies: If you select Escalation Policies, you must select an existing escalation policy from the drop-down list or create an escalation policy. For more information, see Configure an escalation policy.
      Note To view the details of the selected policy, click Details.
    Ticket system Select the ticket system to which alert notifications are sent. For more information about how to integrate a ticket system with ARMS, see Use a Jira account to integrate Jira with ARMS.
  8. After the configuration is complete, click The Save icon in the upper-right corner.

Manage the notification policy

After you create a notification policy, the policy is displayed in the Notification policy list section. You can manage notification policies in the Notification policy list by using one of the following methods:

  • Click the More icon next to the notification policy that you want to manage and select Edit, Disable, Enable, Copy, or Delete.
  • Click the notification policy that you want to manage. Then, you can click the icons in the upper-right corner to modify, refresh, copy, or delete the notification policy.