Indeed, this is a much harder problem to solve than people think. It relies on delaying notifications, which is usually not a good idea, and would then likely only work on a per-contact basis.

It's also only really relevant to email, since as Tom says most other transports aren't really compatible with the idea of alert batching.

For complex alert tracking on large networks I'd always recommend using an external alert management platform like VictorOps or PagerDuty. They'll let you do a lot more.

Adam.

From: observium observium-bounces@observium.org On Behalf Of Tom Laermans via observium Sent: 02 June 2020 20:49 To: observium@observium.org Cc: Tom Laermans tom.laermans@powersource.cx Subject: Re: [Observium] Observium Feature Request - Summarizations for Alert Emails

Hi Anthony,

There is no such 'state' in Observium at this point; it'd also have to be a special case specific for e-mail I think, because other alerting "transports" (= what does the alerting in Observium) can't fit (SMS), parse (Shellscript exec) or don't want to (PagerDuty, VictorOps) have such things summarized.

So just as to why that won't be a simple implementation in 5 minutes. But not saying it can't be done. ;-)

Tom

On 6/2/2020 8:09 PM, Pisano, Anthony D. via observium wrote:

Hello,

I would like to make a feature request for alerts.

Over the weekend a significant portion of campus lost power, generating an overwhelming flood of device down email notifications.

Would it be possible add an option to hold off sending notifications until the current Alerting process has run, and then send a digest or summary of all devices sending alerts?

Thanks

Anthony Pisano | Network Design Engineer | IMSS mailto:anthony.pisano@caltech.edu anthony.pisano@caltech.edu | tel:(626)%20395-4255 (626) 395-4255 | Caltech | caltech.edu http://caltech.edu

_______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium