Creating a Suppression Rule
By using suppression rules, you can suppress or block notifications related to specific alarms. For example, when a major alarm is generated, less severe alarms can be suppressed. Another example, when a node is faulty, all other alarms of the processes or containers on this node can be suppressed.
Precautions
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 up to 100 suppression rules.
Procedure
- Log in to the AOM 2.0 console.
- In the navigation pane, choose Alarm Management > Alarm Noise Reduction.
- On the Suppression Rules tab page, click Create and set parameters such as the rule name and source alarm.
Figure 1 Creating a suppression rule
Table 1 Setting a suppression rule Category
Parameter
Description
-
Rule Name
Name of a suppression rule.
Enter up to 100 characters and do not start or end with an underscore (_). Only letters, digits, and underscores are allowed.
Enterprise Project
Enterprise project.
- If you have selected All for Enterprise Project on the global settings page, select one from the drop-down list here.
- If you have already selected an enterprise project on the global settings page, this option will be dimmed and cannot be changed.
Description
Description of a suppression rule. Enter up to 1024 characters.
Suppression Rule
Source Alarm
Alarm that triggers suppression.
Value range and description:
- Alarm Severity: severity of a metric or event alarm. Options: Critical, Major, Minor, and Warning. Example: Alarm Severity Equals to Critical
- Resource Type: resource type selected when you create an alarm rule or customize alarm reporting. Options: include host, container, and process. Example: Resource Type Equals to container
- Alarm Source: name of the service that triggers the alarm or event. Options: include AOM, LTS, and CCE. Example: Alarm Source Equals to AOM
- Tag: alarm identification attribute, which consists of the tag name and tag value and can be customized. Example: Tag aom_monitor_level Equals to infrastructure
- XX Exists: indicates the alarm whose metadata contains parameter XX. Example: For Alarm Source Exists, the alarms whose metadata contains the provider will be filtered.
- XX Regular Expression: indicates the alarm whose parameter XX matches the regular expression. Example: For Resource Type Regular Expression host*, the alarms whose resource type contains host will be filtered.
Rule description:
A maximum of 10 parallel conditions can be set for root alarms, and a maximum of 10 serial conditions can be set for each parallel condition. Serial conditions are in the AND relationship whereas parallel conditions are in the OR relationship. An alarm must meet all serial conditions under one of the parallel conditions.
Example: For a serial condition, if Alarm Severity is set to Critical, critical alarms are filtered out as the root alarms.
Suppressed Alarm
Alarm that is suppressed by the root alarm.
Set parameters for the suppressed alarm in the same way that you set parameters for the source alarm.
If Alarm Severity is set to Critical in the source alarm's serial condition and set to Warning in the suppressed alarm's serial condition, warnings will be suppressed when critical alarms are generated.
- Click Confirm.
After a suppression rule is created, it will take effect for all alarms that are grouped.
More Operations
After creating a suppression rule, perform the operations listed in Table 2 if needed.
Operation |
Description |
---|---|
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 . |
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