prometheus / prometheus/alertmanager
Receiver filter matching incorrectly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
The receiver dropdown/type ahead filter uses an algorithm to determine the weight of every receiver and bases the order of the results on that. It additionally caps the result set at 10 items. The mix in of filter properties made it harder for me to form a mental model of the behavior. I'd suggest to use a more straight forward approach, use a filter and always keep the alphabetical order. Like the file search in Github or most editors.
Example:
Type: prodeng
Expected: /p.*r.*o.*d.*e.*n.*g/
Unexpected:
backend-engineering-productivitywhich includes all characters from prodeng, but in the wrong orderosc-reportingdoesn't even include all characters.
@stuartnelson3
Contributor guide
No contributing guide indexed for this repository
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 at the receiver dropdown/type-ahead filter described in the issue and trace how its matching and result ordering are implemented. Replace the current behavior only if the project context confirms it, so prodeng matches characters in order and results remain alphabetical; verify the examples from the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100