Configuring Alarm Masking for an MRS Cluster
If you do not want FusionInsight Manager to report specified alarms in the following scenarios, you can manually mask the alarms.
- Some unimportant alarms and minor alarms need to be masked.
- When a third-party product is integrated with MRS, some alarms of the product are duplicated with the alarms of MRS and need to be masked.
- When the deployment environment is special, certain alarms may be falsely reported and need to be masked.
Once an alarm is masked, any new alarms with the same ID will no longer appear on the Alarm Management page or be counted. However, previously reported alarms will still be displayed.
This section applies only to MRS 3.x or later.
- Log in to FusionInsight Manager.
- Choose O&M > Alarm > Masking Setting.
- In the Masking Setting area, select the specified service or module.
- Select an alarm from the alarm list.
Figure 1 Masking an alarm
The information about the alarm is displayed, including the alarm name, ID, severity, masking status, and operations can be performed on the alarm.- The masking status includes Display and Masking.
- Operations include Masking and Help.
You can filter specified alarms based on the masking status and alarm severity.
- Set the masking status for an alarm:
- Click Masking. In the displayed dialog box, click OK to change the alarm masking status to Masking.
- Click Cancel Masking. In the dialog box that is displayed, click OK to change the masking status of the alarm to 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