Ability for routing tree editor to print only subtree matching alert
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 717
- Forks
- 1.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 19
Description
In some cases, a complex alerting manager config with many routes and receivers can result in a graph that becomes almost impossible to read in the routing tree editor. It would be convenient if it had the ability to also print out the whole sub-tree (including the matched yaml config blocks) a given set of labels has matched. It would also be nice if amtool config routes test command could also print this information and not just the end state receivers that match the given labels.
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
Start with the routing tree editor and the amtool config routes test command named in the issue, then trace how matched labels are represented. Done means both surfaces can show the matched subtree and corresponding YAML blocks, rather than only the final receivers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100