We have a complicated alarm pipelines setup. First up, we’re using calculated rosters. On top of that, each user can get distinct messages based on their timezone or other factors using this method. Now, we want to add a rate limiter, and consolidation looks like a good possibility, but I’m unsure if that’s usable after all the other customization.
I’ve not found any detailed discussion of how alarm consolidation does it’s thing. The documentation only shows an example using a simple repeated message, which would not be compatible with my customized messages. Is there any way that consolidated messages can use custom messages similar to the CustomEmailMessage, CustomSmsMessage, and CustomEmailSubject properties?
Beyond that, will the consolidation system be confused by how we split alarm events and use distinct calculated rosters on each? Does consolidation aggregate messages based on the same recipient SMS/email or the alarm source tag or some other key?
Is there perhaps some other simpler method to get alarm notification rate limiting? I was looking at adding delays on the alarm configs, but then the users would receive no alarm at all if a tag crossed back and forth over a threshold within those time limits. We need our system to send at least one message in those cases, so I don’t think those delays would work for us.