influxdata / influxdata/influxdb
Alarm push error lifting
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. new a checks
2. new a NotificationEndpoints
3. new a NotificationRules
__Expected behavior:__
If the URL of notificationendpoints is unavailable and the conditions of notificationrules are met, the alarm should be notificationendpoints instead of notificationrules.
__Actual behavior:__
If the URL of notificationendpoints is unavailable, the conditions of notificationrules are met, and the alarm is notificationrules instead of notificationendpoints.
__Environment info:__
*Ubuntu
* InfluxDB 2.1.1
Contributor guide
Research direction
Reproduce the behavior by creating checks, NotificationEndpoints, and NotificationRules on Ubuntu with InfluxDB 2.1.1. Compare which resource is reported when the endpoint URL is unavailable and the rule conditions are met; done means the alarm identifies the notification endpoint as described under Expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100