Root Time and Root Alarm ID does not change when masking the alarmed parameter

Solved737 viewsmasked
0
1 Comment

Hello,

I have masked the parameter called ‘Param1’ and when I tried to change the alarm severity from normal to critical, it should show new root time and root alarm ID. Instead, it keeps showing the same root time and root alarm ID. Is this behavior expected in the masked alarm console?

For the alarm template, I have set the auto clear as ‘True’ as well.

Thank you.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 17th October 2023
Marieke Goethals [SLC] [DevOps Catalyst] commented

As this question has been inactive for a long time, we will now close it. If you want further assistance, could you post a new question?

1 Answer

7
758 2 Comments

Hi,

This is expected if you do “Mask the alarm for a limited period of time” or “Mask alarm until unmasked”.
Then we keep the alarmtree open to ensure it’s still masked if the parameter goes into alarm again.

If you do “Mask alarm until cleared”, the alarm will close when the parameter isn’t in alarm anymore.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 17th October 2023
Min Thant Aung [SLC] [DevOps Advocate] commented

Hello Tom, thank you for the info.
Also would like to clarify that, when the alarm status is in ‘clearable’, the root alarm ID will not change when the alarmed severity occurs as well?
Marieke Goethals [SLC] [DevOps Catalyst] commented

Hi,
I noticed that this question has been inactive for some time. If you still need more information, could you clarify what you mean with this last comment? Or if the question is fully answered for you, could you select the answer (using the ✓ icon)?