I am trying to understand why there is a vast difference with alarms when you apply history tracking and with history tracking enabled, it condenses the alarms down to just 4 per instance?
If it is the same alarm that is coming and going (due to rain fade in this case) there were some 67 alarms. Once history tracking was applied as a filter, the alarm count had reduced to just 16.
This has caused some confusion and misdiagnosis of faults as there were clearly more alarms to indicate there was an issue onsite.
Does anyone else experience the same kind of filtering in Cube?
I'm asking this because we still have users on System Display (Plan is to migrate them over very soon and upgrade) who have been interpreting alarms a particular way in System Display and moving over to Cube is displaying or highlighting alarms very differently which is probably why the current operators a hesitant to move over.
Hi Nathan,
In addition to the other answers, I compared the behavior between System Display and Cube.
When requesting the alarm history with System Display, it's showing all alarms by default without history tracking, as can be seen below it's showing that there are 110 alarms in the list:
When requesting the alarm history with Cube, it's also showing all alarms by default without history tracking. As can be seen below it's also showing the same 110 alarms in the list:
When activating history tracking in System Display, it's grouping the alarms and show now that there are 49 alarms:
When activating history tracking in Cube, it's also grouping the alarms and show the same thing like in System Display with the same count of 49 alarms:
I also checked if it's possible to see more than 4 entries per alarm group and I can confirm that this is possible. In below example I have an instance that contains 6 children:
Do note when an alarm clears (goes to normal severity) and later on a new alarm is raised that this will be considered as a new instance.
To summarize: I see no difference in the behavior between System Display and Cube. Both show the same alarms and have the same default settings for history tracking. I also see no limit by default in the number of children of an alarm history track, going above 4 seems possible (I checked both the active alarms tab page and also a history tab page).
*Note that the default behavior to always open an alarm console tab with or without history tracking active can be changed in the settings.
Thanks for your response Laurens.
This is great feedback!