influxdata / influxdata/influxdb
Configure statuses in checks
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Proposal:__
Allow users to create more than 4 statuses to checks.
__Current behavior:__
Currently you can only create 4 statuses: "CRIT", "INFO", "WARN", and "OK".
__Desired behavior:__
Users can create and name additional statuses.
__Alternatives considered:__
Manually mapping other statuses with map() and assigning "CRIT", "INFO", "WARN", and "OK" arbitrarily.
__Use case:__
Not all monitoring use cases fit nicely into those 4 statuses. Especially in IoT application development, a status might look like "increasing", "decreasing", "charging", "discharge", "cooling", "heating", "stationary", "moving", etc.
Related to [influxdata/flux#3075](https://github.com/influxdata/flux/issues/3075)
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the checks status model and the code enforcing the four-status limit, then review the related Flux issue; done means users can create and name additional statuses.
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