Kapacitor: Implement Rate limiting for sending alerts

Created on 24 Aug 2016  路  12Comments  路  Source: influxdata/kapacitor

If a Kapacitor task starts to create a siginificant volume of alerts its not helpful to just keep spamming the alerting integration endpoints. Kapacitor should have some kind of rate limit per alert integration where we don't send alerts if Kapacitor is being to spamy.

new-feature

Most helpful comment

This feature would be very useful for us!

All 12 comments

The possiblity of grouping alerts into a single alert would be helpful instead of just rate limiting the output.

@elvarb I am looking for feedback on how you would like the grouping of alerts to behave. Do you have any suggestions on how you would want this to behave? I have a few ideas ...

  • Simplest but probably not that useful would be to concatenate all the alert messages into one large message.
  • Use a template to allow defining the message yourself. For example: {{ .NumAggregated }} alerts are firing\nAlerts {{ range .Alerts }} {{ .Message}} {{end}}
  • Something else entirely?

It would be nice if you could aggregate based on time period and tags in the alert. (e.g. create a single aggregate alert for a count of all alerts of type foo on host type bar within the last minute)

I think it would be nice to set a threshold for each alert targets in tick definition and then when whichever alert exceeds its threshold then kapacitor can start being lazy to send out the repeated alerts (all in the same level) by increasing the interval (simply swallow repeated alerts in between)

Hi, I perfectly agree with @bfgoodrich
Have new features been implemented in 1.3? @nathanielc

@nathanielc, is Kapacitor still not offering a way of rate limiting alerts? I am trying to dig it up in the docs but can't find anything that indicates that..

@m4ce, have you found any workaround?
It would be great if it worked like @bfgoodrich suggested

Any updates?

I'm also interested in rate limiting alerts

It will be great to have such mechanism. Instead of storm message send aggregate statistic with number of suppressed alert messages grouped by AlertName every N minutes.

Any updates on this? I Am also interested in :
I think it would be nice to set a threshold for each alert targets in tick definition and then when whichever alert exceeds its threshold then kapacitor can start being lazy to send out the repeated alerts (all in the same level) by increasing the interval (simply swallow repeated alerts in between)

This feature would be very useful for us!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rconn01 picture rconn01  路  6Comments

phemmer picture phemmer  路  5Comments

ygtzf picture ygtzf  路  5Comments

juise picture juise  路  7Comments

seletskiy picture seletskiy  路  3Comments