yeah alarm overrides are generally a nightmare since any overridden property in an alarm overrides the entire thing and keeps any changes in the UDT definition from getting rolled out. Really annoying problem by itself
1 Like
I can get away with it for the one gateway I’m having the issue with so far, as they don’t have any alarms they want Auto-Ack’d, so I’m simply using the filter extension on the journal to filter out all where ackUser = “tag:Auto-Ack”
We utilize devices that can sometimes lose connection and reconnect with alarms in an Active State, so it is important for us to use Notify on Initial Events.
Of course, this comes with a few pain points, and we ran into issues where we were flooded with Clear alarms, especially after a Gateway restart.
We discovered that our pipelines were set up with a Dropout Condition Acknowledged set to False. As mentioned above, Cleared alarms were automatically Ack’d and thus entered the pipeline notifications.
We also had a few alarms where Ack Mode was set to either Unused or Auto, which was the inclination behind our dropout condition of Acknowledged being false.
2 options to help circumvent this issue.
- Set your dropout condition for Acknowledged to True, and subsequently set your Ack Mode to Manual. Then you can choose whether or not to send an Ack Link. This will prevent Clear alarms from sending on an Initial Event.
- If the dropout condition in your set up is require to be False for Acknowledged you can set an expression block to filter out Initial Events that are Cleared.
