influxdata / influxdata/influxdb
Give the ability to access the flux code behind a check and notification rule
Open
Nobody has claimed this yet.
kind/enhancement
monitoring-and-alerting
team/ui
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
from a user: he would like to be able to quickly debug a check or notification rule. in order to do that, he would like to be able to see the flux code being run behind the scenes.
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
The issue names checks, notification rules, and the Flux code run behind them, but no files or tests. Start by locating the check and notification rule implementations and how their Flux code is executed. Done should make that underlying code accessible to users for debugging.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100