influxdata / influxdata/kapacitor
Implement Rate limiting for sending alerts
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by identifying how Kapacitor sends alerts to each integration and where per-integration delivery policy could be defined. Clarify the desired rate-limit behavior, configuration, and handling of suppressed alerts before implementing it. Done means alert integrations no longer receive excessive alert volume while normal alert delivery remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100