Creating an AOM Alarm Suppression Rule
By using suppression rules, you can suppress or block notifications related to specific alarms. For example, if a major alarm is generated, the alarms of lower severities can be suppressed. If a node is faulty, all the alarms of the process or container on the node can be suppressed.
Constraints
- If the source alarm corresponding to the suppression condition is cleared before the alarm notification is sent, the suppression rule becomes invalid. For the suppressed object (alarm suppressed by the source alarm), the alarm notification can still be sent as usual.
- You can create a maximum of 100 suppression rules. If this number has been reached, delete unnecessary rules.
- Orchestration only applies to the alarms triggered by Prometheus and log monitoring-related alarm rules.
Procedure
- Log in to the AOM 2.0 console.
- In the navigation pane, choose Alarm Center > Alarm Noise Reduction. On the Suppression tab page, click Create.
- Set the basic information about a suppression rule.
Table 1 Basic information about the suppression rule Parameter
Description
Rule Name
Name of a suppression rule. Enter a maximum of 100 characters and do not start or end with an underscore (_). Only letters, digits, and underscores 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 suppression rule, wait for about 10 minutes after the enterprise project is created.
Description
Description of a suppression rule. Enter up to 1,024 characters.
- Set Impact On.
- Specific grouping rule: applies to the alarms triggered by the alarm rule bound to a specific grouping rule. The alarm rules that are not bound to the specific grouping rule will not be impacted.
- Any grouping rule: applies to the alarms triggered by the alarm rule bound to any grouping rule. This option has a wide impact. The alarm rules whose alarm mode is set to Direct alarm reporting will not be impacted.
- Orchestrate the suppression rule. Source alarms will suppress other alarms. Suppressed alarms are those alarms suppressed by source alarms.
For example, if the source alarm's serial condition is Alarm Severity Equals To Critical and the suppressed alarm's serial condition is Alarm Severity Equals To Warning, warnings will be suppressed when critical alarms are generated.
- Click
. Then you can select And or Or to configure filter conditions.
- And: An alarm is triggered only when all conditions are met.
- Or: An alarm is triggered when any condition is met.
- Click
to nest filter conditions. - Click
to set multiple filter conditions.
Table 2 Filter condition parameters Parameter
Description
Example
Alarm Severity
Severity of a metric or event alarm. Options: Critical, Major, Minor, and Warning.
Alarm Severity + Equals To + Critical
Resource Type
Type of the resource selected when you create an alarm rule or configure custom alarm reporting. Options: include Service and Cluster.
Resource Type + Equals To + Cluster
Alarm Source
Name of the service that triggers an alarm or event. Options: include AOM, LTS, and CCE.
Alarm Source + Equals To + AOM
Tag
Alarm identification attribute. It consists of a tag name and tag value and can be customized.
Tag + resource_type + Equals To + AOM
Alarm Rule's Enterprise Project
Enterprise project specified when the alarm rule is created. You can select the corresponding enterprise project.
Alarm Rule's Enterprise Project + Equals To + default
Original Rule Name
Original alarm rule name configured during rule creation. Enter the original name of the alarm rule.
Original Rule Name + Equals To + AOMAlarm
Annotation
Configured during alarm rule creation. It is an attribute that cannot be used to identify alarms. It consists of an annotation name and annotation value and can be customized.
Annotation + aom_monitor_level + Equals To + infrastructure
First Triggered
Time range when an alarm is triggered for the first time. You can select Within Range or Out of Range for matching.
First Triggered + Within Range + 2025.04.08 15:26 — 2025.04.08 16:26
-
Matching conditions:
- Exists: XX + Exists + AA. This means that the alarm whose XX contains AA is filtered. For example, Tag + Exists + AOM indicates that the alarm whose tag contains AOM is filtered.
- Not Exist: XX + Not Exist + AA. This means that the alarm whose XX does not contain AA is filtered. For example, Tag + Not Exist + AOM indicates that the alarm whose tag does not contain AOM is filtered.
- Matches Regular Expression: XX + Matches Regular Expression + Expression. This means that the alarm whose XX matches the specified regular expression is filtered. For example, Resource Type + Matches Regular Expression + host* indicates that the alarm whose resource type starts with host is filtered.
- Not Match Regular Expression: XX + Not Match Regular Expression + Expression. This means that the alarm whose XX does not match the specified regular expression is filtered. For example, Alarm Source + Not Match Regular Expression + LTS* indicates that the alarm whose alarm source does not start with LTS is filtered.
Equals To, Not Equal To, Within Range, and Out of Range are not described in detail herein.
-
- Click
- Click OK.
More Operations
After creating a suppression rule, perform the operations listed in Table 3 if needed.
|
Operation |
Description |
|---|---|
|
Viewing a suppression rule |
Click the name of a suppression rule in the rule list to view its details. |
|
Modifying a suppression rule |
Click Modify in the Operation column. |
|
Deleting a suppression rule |
|
|
Searching for a suppression rule |
Enter a rule name in the search box in the upper right corner and click |
|
Setting column display |
Click in the upper right corner of the list. In the displayed dialog box, set column display.
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot

