Creating an AOM Alarm Notification Rule

Prerequisites

• You have created a topic. For details, see Creating a Topic.
• You have configured a topic policy. For details, see Configuring Topic Policies.
• You have added a subscriber (that is, an email or SMS message recipient) for the topic. For details, see Adding a Subscription to a Topic
• To obtain SMN topics when creating a notification rule, you must obtain the smn:topic:list permission in advance. For details, see SMN Permissions.

Constraints

• You can create up to 1,000 alarm notification rules. If this limit has been reached, delete unnecessary rules.

Creating an Alarm Notification Rule

1. Log in to the AOM 2.0 console.
2. In the navigation pane, choose Alarm Center > Alarm Notification.
3. In the right pane, click the Notification Rules tab and click Create.
4. Set the notification rule name, type, and other parameters by referring to Table 1.
   Figure 1 Creating an alarm notification rule
   

   Table 1 Alarm notification rule parameters

   Parameter	Description
   Notification Rule Name	Name of the notification rule. Enter up to 100 characters and do not start or end with an underscore (_), hyphen (-), or period (.). Only digits, letters, underscores, hyphens, and periods are allowed.
   Enterprise Project	Enterprise project. If Enterprise Project is set to All on the global settings page, select an enterprise project from the drop-down list here. If you have already selected an enterprise project on the global settings page, this option will be grayed and cannot be changed. To select the newly created enterprise project during the creation of an alarm notification rule, wait for about 10 minutes after the enterprise project is created.
   Description (Optional)	Description of the notification rule. You can enter up to 1,024 characters.
   Rule Type	Notification rule type. Prometheus monitoring If a metric or event meets the alarm condition, the system sends an alarm notification based on the associated recipient and message template. Log monitoring If the log data meets the alarm condition, the system sends an alarm notification based on the associated recipient and message template.
   Rule Settings	You can select Simple or Orchestrated. Simple: You can directly configure the notification scope. For details, see Notification Scope. Orchestrated: You can configure the alarm condition and notification scope. For details, see Orchestrate Notification Rule.
   Notification Scope	Notification scope of the alarm notification rule. When Rule Settings is set to Simple, you can directly configure the notification scope. Recipient: recipient to which the alarm notification is sent. You can select a subscription topic. Select an existing topic. If no topic meets your requirements, create one on the SMN console. For details, see Creating a Topic. Days: Select the days for sending alarm notifications. Valid From: Alarm notifications are only sent during the configured validity period. If Valid From is set to 08:00-20:00, notifications are sent only within 08:00-20:00. Message Template: Select a message template from the drop-down list. AOM provides preset message templates. If the preset templates do not meet requirements, click Create Template to create one. For details, see Creating AOM Alarm Message Templates. Click Add Notification Setting if needed. Click Delete to delete notification settings. At least one notification setting must be available.
   Orchestrate Notification Rule	You can define the entire notification process. Alarms that meet the specified conditions are filtered and corresponding notifications will then be sent. When Rule Settings is set to Orchestrated, you need to orchestrate a notification rule. There are three types of operations: Add Condition, Add Notification, and Add End Node. You can click to enter the full-screen mode. Click Add Condition to add an alarm condition. Parameters: Alarm Severity: severity of a metric or event alarm. Options: Critical, Major, Minor, and Warning. You can select Equals To for matching. Example: Alarm Severity + Equals To + Critical Resource Type: type of the resource for which an alarm or event is generated, such as Service or Cluster. You can select Equals To or Matches Regular Expression for matching. Example: Resource Type + Equals To + Cluster Alarm Source: name of the service for which an alarm or event is generated, such as AOM, LTS, or CCE. You can select Equals To, Not Equal To, Matches Regular Expression, or Not Match Regular Expression for matching. Example: Alarm Source + Equals To + AOM Tag: configured when an alarm rule is created. A tag is an attribute that can be used to identify alarms and will be synchronized to TMS. A tag consists of a tag key and tag value. You can select Equals To, Not Equal To, Exists, Not Exist, Matches Regular Expression, or Not Match Regular Expression for matching. Example: Tag + resource_type + Equals To + AOM. Alarm Rule's Enterprise Project: enterprise project configured when an alarm rule is created. You can select Equals To or Not Equal To for matching. Example: Alarm Rule's Enterprise Project + Equals To + default Alarm Status: alarm status, which can be Alarms or Alarm Clearance. You can select Equals To or Not Equal To for matching. Example: Alarm Status + Equals To + Alarms Original Rule Name: original name configured during alarm rule creation. You can select Equals To, Not Equal To, Matches Regular Expression, or Not Match Regular Expression for matching. Example: Original Rule Name + Equals To + AOMAlarm. Alarm Duration: duration of the alarm, in seconds. You can select =, >, <, ≥, or ≤ for matching. Example: Alarm Duration ≥ 20. Annotation: configured when an alarm rule is created. An annotation is an attribute that cannot be used to identify alarms and will not be synchronized to TMS. An annotation consists of an annotation key and annotation value. You can select Equals To, Not Equal To, Exists, Not Exist, Matches Regular Expression, or Not Match Regular Expression for matching. Example: Annotation + aom_monitor_level + Equals To + infrastructure First Triggered: time range when the alarm is first triggered. You can select Within Range or Out of Range for matching. Example: First Triggered + Within Range + 2025.04.08 15:26 — 2025.04.08 16:26. Cleared: time range when the alarm is cleared. You can select Within Range or Out of Range for matching. Example: Cleared + Within Range + 2025.04.08 15:26 —2025.05.15 16:26. Alarm conditions can be configured using And and Or. Click to configure multiple alarm conditions. Click to nest alarm conditions. Configure the alarm notification scope in the area pointed to by the Yes arrow. For details, see Notification Scope. Configure the subsequent processing if the alarm conditions are not met in the area pointed to by the No arrow. If needed, click Add Condition to add more alarm conditions. If you do not need more alarm conditions, click Add Notification to configure the notification scope. If you do not need more alarm conditions or notification settings, click Add End Node to end the orchestration process. If alarm conditions are not needed, directly click Add Notification to configure the notification scope.

5. Click OK. The rule will then be created. You can then perform the following operations:
   • Go to the Alarm Noise Reduction page, create a grouping rule, and associate it with the notification rule. (Alarm grouping rules cannot be associated with the alarm notification rules for which orchestration has been configured.)
   • Go to the Alarm Rules page, create an alarm rule, and associate it with the notification rule.

More Operations

After an alarm notification rule is created, you can perform the operations listed in Table 2.

Reference

If no notification message is received, rectify the fault by referring to Why Do Subscribers Fail to Receive Messages After I Publish Messages to a Topic?