Hi Dojo,
we have experienced the following:
When we mask an alarm for a specific time period, this masking remains even after the time period has ended. The underlying alarm may have resolved in the meantime, but the associated parameter remains masked. Since no alarm state exists, there is consequently no entry in the list of masked alarms. This phenomenon can only be resolved by artificially triggering the alarm state and then manually lifting the masking to restore the original state.
Is this behavior to be expected? In our view, the masking of the parameter should definitely end once the defined time period has elapsed, regardless of any existing or resolved alarm states.
Thank you! 🙂
Hi Nils,
This behavior is not expected. When the masking period has ended, the parameter should be fully monitored again regardless its passed alarm states. I just did a quick test and I couldn't reproduce the behavior you described (test was done server version 10.4.12 & client version 10.5.2501). This could be a specific issue in your setup/version. I think it is best to handle this via the regular support to further follow up.
Cheers Koen.
Hi Koen,
thanks a lot for your reply and for testing. I've tried my best to reproduce this behaviour on our staging system (including automated alarm template switching to simulate flapping alarm states of the parameter), but everything behaves as expected – the masking of the parameter doesn't get stuck, just as usual.
So I'll consider this to be an abnormal singularity. 😉