Hi – we have an issue that we are seeing lots of “properties changed” entries. We would like to update the alarm properties without having a “properties changed” alarm entry.
The alarms are from a table. I.e. we have a table where a column is the alarm severity – which is included in the alarm template.
I have been told we can use the doUpdateOnAlarmValueChange flag, but I don’t know where/how this is used and can’t find any mention of it in the documentation.
Could anyone point me at the documentation or explain how it works here – particularly when used with table entries.
Introduced in 9.5.12, a custom property on an element, service or view has a option called ‘Update alarms on value changed’. This is by default checked, so set to true, but can be disabled. When disabled, a updated value for this specific custom property will no longer cause a new alarm.
The option is available when creating or updating the custom property
More information on this functionality can also be found on DataMiner Help. (item 5 of ‘Adding a custom property to an item’)
This sounds like a good use case for a feature we internally call “Alarm Squashing”. When Alarm Squashing is enabled, DataMiner will no longer show a separate alarm for every property change.
More information about Alarm Squashing can be found in this blog post, Declutter your alarm tree.
Unfortunately, I can’t seem to find any reference to this ‘doUpdateOnAlarmValueChange’ flag. Would you have some more information on this flag, would this be something defined in the driver/protocol or a general DataMiner setting? It would also be useful to know which DataMiner version you are using to determine if there’s a workaround for what you want to achieve.
Thanks for the answer – looks like what we need, but could you help me with the original question as well so I can progress that investigation as well. Thanks