influxdata / influxdata/influxdb
Notifications for threshold checks not working correctly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
I noticed that thresold check notifications dont work as expected. I am using the official ubuntu package version 2.0.9 of influxdb2. While using for example a "disk usage" threshold check (telegraf metrics) for about 10 linux servers following behaviour can be observed:
When i set the field "Schedule Every" to 1m everything works fine, the notification rules send an email on to high disk usage as expected. In order to avoid flapping between to states (in case of short time higher usage) i want rather to send only once an hour a notification. So setting the field "Schedule Every" to 1h does change the states every hour but the corresponding notifications ar not beeing sent. Same behaviour for any other value than 1m. My notification rule is applied every 1m with an offset of 10s,
If any further information is required please reply.
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
Reproduce the issue using threshold checks, notification rules, and the Schedule Every setting described in the report, comparing 1m with 1h and other intervals. Trace the threshold-check scheduling and notification dispatch paths, then verify that a state change at intervals other than 1m sends the expected notification without altering the 1m behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ubuntu
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100