Serverless App Engine:Notification policy

Prerequisites

Before you begin, ensure that you have:

• Created contacts to receive alert notifications

Create a notification policy

1. In the SAE Application List, select the target region and namespace, then click the Application ID to open the application page.

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

3. In the editor on the right, enter a name in the Name field.

4. In the Match alert event rules section, configure the matching conditions.

   a. Select a data source.

   Option	Behavior
   Specific data source	ARMS applies your matching rule to events from that source only.
   No Preset Source	ARMS applies your matching rule to all alert events, regardless of origin.

   b. Set the matching rule expression.

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

   Two types of existing tags are available:

   • Fields included in an alert rule expression. To create tags for an alert rule in Managed Service for Prometheus, see Create an alert rule for a Prometheus instance.

   • Default tags provided by ARMS, listed in the following table.

   Category	Label	Description
   Common fields	alertname	The alert name.
   	clustername	The cluster name.
   	severity	Alert 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 value for ARMS alerts 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.

   To control how the expression evaluates multiple conditions:

   • Click + Add Condition to add a matching condition in the same rule — the alert is triggered when all conditions in the rule are met simultaneously.

   • Click + Add Rule to add a separate matching rule — the alert is triggered when any single rule's condition is met.

5. In the Event handling section, choose how matched events are processed.

   To reduce alert noise, enable intelligent noise reduction. In the left navigation pane, choose Alert Center > Alert Event History. On the Events page, turn on Intelligent Analysis. For details, see Configure intelligent noise reduction.

   Parameter	Description
   Processing method	Compress (default): Groups matching events and compresses them into a single alert. One event can match multiple notification policies and generate separate alerts for each. Silence: Suppresses alerts for matching events. Silenced events are not evaluated by any other notification policy. Silence takes priority over Compress.
   Effective period	Available only when Processing method is set to Silence. Options: Permanent, Recurring, or Custom Time Period.
   Advanced settings	Available only when Processing method is set to Compress. Includes two sub-settings: Event grouping — Do Not Group (default) sends all alerts in a single notification. Assign Events With The Same Field Content To A Group sends separate notifications for events that share the same field values. Automatic Alert Resolution — Enabled by default. When all related events return to the Restored state, the alert is marked as Resolved and a notification is sent to the contacts.

6. In the When an alert is triggered section, configure notification recipients and delivery settings.

   Parameter	Description
   Contacts/Schedules	Add contacts, contact groups, DingTalk groups, or on-call schedules. To create a contact, see Create a contact.
   Notification methods	Select one or more channels: DingTalk, email, text message, phone, or Webhook. Phone notifications require a verified mobile number. Click Notification Template to customize 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	Choose how to handle unresolved alerts: Recurring notifications resends at a set frequency during the notification period. Escalation policy routes to other contacts if the alert remains unresolved — click Details to view the policy, or see Escalation policy to create one. Do Not Resend Notifications
   Ticket system	Push alerts to a connected ticket system. For setup instructions, see Integrate with the Jira ticket system using Jira account information.

7. Click Save.

The 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 it.

What's next

• Create a contact to add recipients to your notification policy.

• Configure intelligent noise reduction to reduce duplicate alert notifications.

• Create an escalation policy to route unresolved alerts to other contacts automatically.