Hi Dojo, quick follow-up from this older post:
Correlated Alarms & Custom Alarm properties: info not kept in Console when the alarm clears
If some custom alarm properties are still relevant after the alarm has cleared, what are the suggestions to make them persistent?
Working with our squad on a scripting approach, but wondering if this could be marked as possible new software feature, e.g. marking certain alarm properties to keep their value even after the alarm has cleared.
The use case is for subcomponents originating the alarm, currently stored in a custom alarm property.
Thanks
Alberto,
There is since 9.6.11 (RN23067) the possibility to update the properties of a closed alarm. You can follow the example for normal alarms in the docs page:
NT_EDIT_PROPERTY (62) | DataMiner Docs
In the background this will try to fetch the alarm from the database and create a new alarm in the alarm tree and store an update in the alarm tree.