5.3.1. Grouping

Notification maximum frequency

If 100000 messages fall in error in a short period, you surely don't want to receive 100000 notification e-mails.

To achieve that, every agent will have a parameter Notification
maximum frequency, with values ranging from "Maximum 1 notification per hour" to "Maximum 1 notification per week".

This parameter will have no effect on when we will send you the first notification. In all cases, we want to do that quickly. But if some new interesting events come and that this agent already notified you too recently (according to this parameter), the agent will buffer all the new events, and send them in one email as soon as the period is finished.

A consequence is that it is impossible to use message data in the notification text, as the notification will most of the time not refer to a precise message. If you want to send emails for the processing of ONE message, it is still possible, but via extra processings. It will not be a notification, but part of the message processing.

Reminder frequency

For agents that notify you about problems (gateway down, messages in error, …), they will continue reminding you until the problem is fixed, but at a lower frequency than for new problems.

You can configure this using the parameter Reminder frequency, with values ranging from No reminder to One reminder every 7 days.

Full status

When we send a notification, we don’t only notify of new problems, but we will always give a full status at the time of the notification.

For example, if we notified you one hour ago that you had 3 messages in error (that are still not fixed), and now have to notify you of 2 new errors, we will mention the new 2 errors, but also about the total of 5 messages that are now waiting for a fix.