How exactly would this work, Roopa. It makes sense at a high level - don't generate a 100+ emails if there are a hundred plus issues, but if you were writing out directions for a human on how to do this, what exactly would those directions be? I.e. when they see the first error, generate an alert. If they see the second error, how would they know if they should generate an alert or not? Is it by the amount of time that goes by since the first error and as long as that time has not transpired, you don't want to be told again, or is it by the number of those errors that occur, or some combination of factors, or what? I.e., should the instructions be don't generate any more alerts for this error for the next <number> of minutes, hours, or the next 24 hours? And then you can? When can more alerts for this error ever be generated again? The more specific you can be on how this feature would work, the more likely it would be added in a way you would like.
------------------------------
Dale Ander
------------------------------
Original Message:
Sent: Wed October 16, 2024 01:39 PM
From: Roopa Kailar
Subject: Control Center Monitor - Limiting number of alerts
We are using Version 6.3.1 of Control Center Monitor and have written a rule to send out an email when a Business Process in B2B SI processed with errors. Is there a way to limit the number of alerts triggered for the same Business process failure? For example, if BP AS2SendSyncMDN is failing for some reason, there may be 100s or more failures at the same time and we do not want 100+ emails for the same type of BP failure. Any help is appreciated. Thanks!
------------------------------
Roopa Kailar
------------------------------