Help Center/
Edge Data Center Management/
User Guide/
Device Management/
Alarm Management/
Alarm Setting/
Configuring Unhandled Alarm Severity Rules
Updated on 2022-02-21 GMT+08:00
Configuring Unhandled Alarm Severity Rules
Context
- After a rule is enabled, it takes effect for the alarms reported before and after the rule is enabled.
- After the alarm severity is changed, the alarm severity displayed in the alarm list is the new one. However, when you select an alarm for other rules, the alarm severity displayed is still the original one.
- A maximum of 2000 unhandled alarm severity rules can be created.
- By default, the rules are sorted by the enabled and disabled states, and the rules in the same state are sorted by update time in descending order.
Procedure
- Choose from the main menu.
- In the navigation pane, choose Unhandled Alarm Severity Rules.
- On the Unhandled Alarm Severity Rules page, click Create.
- In the Basic Information area, set the rule name, description, and whether to enable the rule.
- In the Conditions area, set the alarm name, alarm ID, group name, and alarm status.
- In the Handling Policy area, set Trigger condition and Action.
- In the Other area, set the priority for the rule.
- Click OK.
Related Tasks
- Deleting a rule: You can select a redundant rule from the rule list and click Delete to reduce the rule maintenance workload.
- Enabling/disabling a rule: You can select a rule that is not used temporarily from the rule list and click Disable. To use a disabled rule, select the rule and click Enable.
Parent topic: Alarm Setting
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot