influxdata / influxdata/kapacitor
Alert rule with retention policy doesn't trigger
Open
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. Add alert rule with retention policy
2. Rule is never triggered
__Expected behavior:__
I expect the rule to trigger an alert
__Actual behavior:__
An alert does not get triggered
__Environment info:__
RHEL 7
Chronograf 1.8.10-1
InfluxDB: 1.8.4
Contributor guide
Research direction
Start by reproducing the alert-rule behavior using the listed RHEL 7, Chronograf 1.8.10-1, and InfluxDB 1.8.4 environment, with a retention policy attached. Trace how Kapacitor evaluates that rule and compare it with a rule without a retention policy; done means the configured rule triggers its alert as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100