Hi,
We observe that when we mask all alarms from an element, the Alarm State of said element translates into “Normal” on Cube.
However, when we trigger the “Alarm State” report for the same element, the State presented is “Unknown”.
In the statechanges table this transition is coded with value 25 (Masked).
Is this an issue? A design decision?
Thank you.
Hi Bruno,
There is a difference between masking alarms from an element and masking the element itself. When masking the element, the state of the element will be ‘Masked’. And wherever your element resides in (e.g. view or service), those will go in ‘normal’ state (in case no other alarms impact the state that object of course).
The same applies for the alarms. When masking an alarm, that alarm goes into a masked state, but the element where the alarm comes from, goes into a ‘Normal state’ (when no other alarms are active on that same element)
State timelines should show the state over time, so should reflect the actual state that was displayed at that time from the past. So in your case, when your element state was ‘Normal’, you should see a green (default ‘Normal’ color) bar.
On my internal test system, I can see an ‘incorrect’ alarm timeline as well, so we might have an issue. Can you further refine your case in a Collaboration task, so we can take a detailed look please?