We are actively working on a solution to this problem. See https://github.com/influxdata/kapacitor/blob/nc-alert-service/ALERT_DESIGN.md The basic idea is that you will be able to both aggregate multiple alerts and rate limit sending alerts. Which should be able to prevent an alert storm
On Tuesday, November 29, 2016 at 6:05:49 PM UTC-7, kho...@gmail.com wrote: > > What is a good way to filter an alert storm? I have Kapacitor watching for > events in a measurement and alerting to PagerDuty if any occur. But in some > circumstances the underlying problem can cause a bunch of matching events > to come through. > > I would like to filter so I raise one event in PagerDuty (or to Slack, > etc) but not raise any more events for some short period of time. > -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+unsubscr...@googlegroups.com. To post to this group, send email to influxdb@googlegroups.com. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/ab16e5e1-eb31-4d9c-9cca-07e685e993f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
