If a part of the service contains elements that may be affected by a climatic event, is it possible to continue monitoring the rest of the elements that make up the service without degrading the SLA? The idea is to ignore those alarms when they are known events, like a storm or maintenance on a specific item.
It seems that masking an alarm does not pause the service degradation for the SLA Definition Basic
Hi Carlos,
Checking old tickets, this behavior should be supported (see internal RN6759). However, I am also able to reproduce the same behavior (after masking an alarm, the SLA outage still degrades). Driver range used: 3.0.0.x
A possible workaround will be to add an extra setting in the service monitored by the SLA. For each element that is part of your service you could add the following condition:
You will also need to update the settings in the SLA:
Advance Configuration -> Service Capping set to Enabled.
Can you also create a task to further investigate this behavior?