influxdata / influxdata/kapacitor
Allow for burn-in when defining dynamic alerts
Open
new-feature
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Since alerts can be based of dynamic criteria it will be nice to have a burn in period so that when its learning stable state it does trigger alerts.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by tracing how dynamic alert criteria are defined and how their learning state triggers alerts; clarify the burn-in duration and expected behavior before identifying the relevant implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100