Hello,
We are experiencing an unwanted behavior on Dataminer 9.6.0 version. Usually the alarms are created with Alarm type “New Alarm” but sometimes when alarms are raised (for elements or services) they get the alarm type “property changes”.
Could you please let me why these alarms are generated and if we can stop them from popping up in the alarm console somehow?
TIA 🙂
Hi Arunkrishna,
Alarms typically have a lifecycle. When a parameter goes from a ‘normal value’ into the ‘warning’ threshold for example, a ‘New alarm’ will be created. In case the value further evolves into another severity threshold, another alarm is created that is linked to the previous one. In the alarm console in DataMiner Cube this results in a ‘tree’ of alarms (when ‘history tracking’ is enabled) showing the most recent alarm on top (in the tree).
In fact, our alarm objects are immutable, once created they never change. Changes always result in a new alarm that is linked to the previous one and is shown op top of the previous one in DataMiner Cube alarm console.
Alarms can have properties and when those change, for the same reason, a new alarm is created, linked to the original one (those get the type ‘property changed’). Again, in DataMiner Cube, this is presented as a new item in the ‘tree’ of alarms.
From 10.0.12 onwards, we have a setting that can (visually) limit the number of alarm ‘updates’: AlarmSettings.MustSquashAlarms
Via this setting, DataMiner Cube will squash different ‘update’ alarms in one and it will look like the alarms are no longer immutable (but this is only presentation, behind the scenes, nothing really changed)
Hope this helped.
One way to verify that is to open the alarm card in Cube (right click the alarm from Cube alarm console) and look in the ‘properties’ section. The property that was updated should have a darker text color.
Thank you Pieter, is there a way to determine which property of the alarm changes when the “properties changed” occurs ?