influxdata / influxdata/kapacitor
feature request: add ability to expire old alert events based on some retention policy
Open
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
It would be great to add the ability to expire old alert events based on some retention policy.
Contributor guide
Research direction
The issue does not name files, tests, or entry points. Start by locating how alert events are stored and queried, then determine where a retention policy could be configured and enforced. Done would require an agreed policy scope, configuration behavior, expiration mechanism, and tests covering old events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100