Alarm pipeline: calculated roster and consolidation

Hello folks !

So, I've been wondering about a few things concerning pipelines' notification blocks.
Imagine I have 2 users, one wants only critical notifications, the other one wants anything above medium.
For some reason, this is done through calculated rosters, something like

roster = []
if event.priority >= critical:
if event.priority >= medium:
return roster

Now, there's also a consolidation set up on this block.
Critical event comes in, both are added to the roster.
10 seconds later, high event comes in, only Ritchie is supposed to get it.

So, what happens there ? Will two different mails be sent, with Jimmy getting a standard one-alarm notification, and Ritchie getting a consolidated one ?

Next question: Can I access collection eventS properties from a calculated roster script ?
Like I'd reference the highest priority in the mail subject with {AlarmEvents.MaxPriority}, is there a way to get this information in the script ?

That's all for now !

It's so quiet in there I can hear my own thoughts.
Please send help.

I haven't done anything like this, but due to how much you help out around here, I really want to lend you a hand. My question would be this: is "critical" a numeric value that can be evaluated with greater than or equal to operators? It looks more like a string value that would require the == operator.

If nothing else, at least I've bumped this back to the top.

1 Like

That's pseudo-code, what it really does is irrelevant.
The point is, one execution of the script returns a different roster than the second one, in a time window that's shorter than the consolidation delay.
I wanna know what happens in this case. Who receives what.

I'm going to guess that you've stumped the lot of us. Testing would be in order.

ew :X
I'm under constraints that make trying this... impractical.
I'll do my best and report back, I guess.

Well... After testing this, I'm not happy with the results.
Let's take this calculated roster (I know the syntax isn't correct, that's not issue here):

roster = [""]
if event.priority >= critical:
return roster

With a consolidation.
Now let's say I send 2 alarms, one critical, one low. Everyone receive the same notification, with both alarms consolidated.

I'll try to think of a way to work around that, but it'd be cool if we had more details about how consolidation/calculated rosters work, and maybe a built-in way to tweak those things.

Coming in since you pinged me on my old related thread.

Sadly, we never found a solution and have had to leave consolidation disabled.

If push comes to shove, my next step is going to be to abandon Ignition pipelines almost entirely, and script EVERYTHING. I would leave a simple pipeline that sends the alarm events to a script, and do all the other management myself. There are APIs to send Twilio messages and emails, which i would use instead of the built-in alarm notification pipeline blocks.

I really wish the built-in consolidation features could consolidate per recipient email or phone-number, and not per event or per pipeline or whatever it does right now.

1 Like

Damn, I was hoping you'd found some black magic to fix all this :X

I'm considering a few pipelines schemes that may or may not yield proper results.
I'll update here when I'm done testing.