We have an alarm pipeline currently set-up to send e-mail notification whenever a value of a tag exceeds reading of 30.
My understanding is this:
One e-mail will send if it was reading 29, then reading 31.
Two e-mail will send if it was reading 29, then reading 31, then 29, then 31.
One e-mail will send if it was reading 29, then reading 31, then 32
I want to change this set-up, where if the reading was above for 3 consecutive events (29, 31, 32, 31), it will send out one e-mail, but none if not reaching 3 consecutive events.
Any idea how I could approach this? Looking for a very simple, if possible, non-scripted way.
Would you help elaborate? All I see is the timing delay, but each of the datapoint events does not occur in same time cycle interval.
For example, the first reading of value 29 might happen after 31 seconds, and the next value of 31 might happen after 3 seconds or 60 seconds. There's a huge variability for me to place a simple timing delay.
Are there per-event count mechanism that I can place, even though the alarm has been triggered already once, to formulate that into Email alarm pipeline?
The alarm system is not going to produce a new alarm if a new value is still in alarm, which is what I meant by "not separate events". Whether the timing is varying or not. Sounds like you are going to have to script your own pseudo-alarm system instead of alarming directly on the values.
Alternatively, you could have another memory tag which has the alarm that counts up each time the monitored tag's value is above the alarm setpoint. Then set the alarm value setpoint to the number of events you want to trigger the alarm on. Reset the tag's value when the monitored tag goes below the sp
I tried this method along with gateway tag change script to make the memory tag to reach 3, and tied the alarm to memory tag to trigger the e-mail and it seems to work! Thank you.