Serverless App Engine:Notification policy

Procedure

1. In the SAE Application List, select the destination region and namespace at the top of the page, and then click the target Application ID to go to the application product page.

2. In the navigation pane on the left, choose Notifications and Alerts > Notification Policy. On the Notification Policies page, click Create Notification Policy.

3. In the editor section on the right, enter a name for the notification policy in the Name text box.

4. In the Match Alert Event Rules section, configure the following information.

   1. 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.

   2. Set the matching rule expression.

      Add custom tags or select existing tags. For example, set alertname equal to memory usage.

      The following types of existing tags are available:

      • The fields that are included in an alert rule expression. For information about how to create a tag for an alert rule in Managed Service for Prometheus, see Create an alert rule for a Prometheus instance.

      • The default tags that are provided by ARMS. The following table describes these tags.

        Expand to view the default tags.

        Category	Label	Description
        Common fields	alertname	The alert name.
        	clustername	The cluster name.
        	severity	The alert severity. The severity levels increase from default, P4, P3, P2, to P1.
        	namespace	Namespace.
        	pod_name	Pod name.
        System-reserved fields	_aliyun_arms_integration_name	The integration name. The default integration name for alerts reported by ARMS is ARMS-DEFAULT.
        	_aliyun_arms_involvedObject_id	The alert object ID.
        	_aliyun_arms_involvedObject_name	The alert object name.
        	_aliyun_arms_region_id	The region ID.
        	_aliyun_arms_alert_rule_id	The alert rule ID.
        	_aliyun_arms_alert_type	The alert rule type: 101: Prometheus alert 5: Application monitoring alert 4: Browser Monitoring alert

      Note

      • If you want an alert to be triggered when multiple conditions are met at the same time, click + Add Condition to add a matching condition in the same matching rule.

      • If you want an alert to be triggered when only a single condition is met, click + Add Rule to add a matching rule.

5. In the Event Handling section, configure the parameters.

   Note

   To adjust the frequency of alert notifications, you can modify the alert rule and configure intelligent noise reduction. In the navigation pane on the left, choose Alert Center > Alert Event History. On the Events page, turn on the Intelligent Analysis switch. For more information, see Configure intelligent noise reduction.

   Parameter	Description
   Processing Method	Compress: By default, this option is selected. Events that match the notification policy are grouped. Events in the same group are compressed into a single alert. An event can match multiple notification rules and generate different alerts. Silence: Events that match the notification policy do not trigger alerts. After an event is silenced, it can no longer be matched by other notification policies. The Silence processing method has a higher priority.
   Effective Period	This parameter is required only if you set Processing Method to Silence. Valid values: Permanent, Recurring, and Custom Time Period.
   Advanced Settings	This parameter is required only if you set Processing Method to Compress. Event Grouping Do Not Group: By default, this option is selected. All alerts are sent to the contacts in a single notification. Assign Events With The Same Field Content To A Group: Select one or more grouping fields. Alerts for events with the same values in the selected fields are sent in separate notifications to the contacts. Automatic Alert Resolution: By default, this feature is enabled. This setting specifies whether an alert is automatically marked as Resolved when all its related events are in the Restored state. The system sends a notification to the contacts when the alert is resolved.

6. In the When an alert is triggered section, configure the following information.

   Parameter	Description
   Contacts/Schedules	Specify one or more contacts, contact groups, DingTalk groups, and on-call schedules. For more information about how to create a contact, see Create a contact.
   Notification Methods	The available notification methods are DingTalk, email, text message, phone, and Webhook. You can select multiple methods. Contacts cannot receive phone notifications until their mobile numbers are verified. For more information about how to verify a mobile number, see Verify a mobile number. Click Notification Template. In the Notification Template dialog box, configure the format for email, text message, and phone notifications.
   Notification Period	Alert notifications are sent repeatedly during the specified notification period.
   Method To Escalate Notifications	For unresolved alerts, choose to resend or escalate notifications to ensure they are handled promptly. Recurring notifications: Set the frequency for sending alert notifications. During the specified notification period, notifications are sent at this frequency until the alert is resolved. Escalation policy: If an alert remains unresolved, notifications are sent to other contacts based on the escalation policy. Click Details to view the details of the selected policy. For more information about how to create an escalation policy, see Escalation policy. Do Not Resend Notifications
   Ticket System	Select the ticket system to which alerts are pushed. For more information about how to integrate with a ticket system, see Integrate with the Jira ticket system using Jira account information.

7. Click Save.

   The new policy appears in the Notification Policy List on the left side of the Notification Policies page. Click the icon next to the policy name to edit, enable, disable, copy, or delete the policy.