In Visual Overview you can auto generate shapes for alarms of an element/view/service.
What's the expected behaviour when masking one of these alarms?
Should it by default hide the shapes from the list, should the color of the shape change to the masked alarm color, ...
Should you use the childrenfilter option instead and specify a shared filter to filter out the masked alarms?
Does it then apply the childrenfilter every time an alarm update enters or only when you open the visual overview?
Marieke Goethals [SLC] [DevOps Catalyst] Edited question 22nd October 2020
The current behavior is as follows:
- The children shape will display all alarms (masker or not) for a given element, view or service.
- The color of the shape (when using '*|Alarm' in the 'Alarm' shape data) will display the severity of the alarm. Masking an alarm does not affect the severity. This means that the masked color is not displayed here. I can understand that this can be confusing and perhaps we should change this behavior (or at least provide a way to display the masked state).
- You can filter out masked alarms by using an alarm filter. This filter will be used for every alarm update. Note that the Alarm Console does not display masked alarms by default, something Visual Overview does. Be sure to exclude masked alarms in your alarm filter.
Marieke Goethals [SLC] [DevOps Catalyst] Changed status to publish 22nd October 2020