prometheus / prometheus/alertmanager
Improve alert indexing and search
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
From @brancz
currently there are various maps to improve access to certain alerts, but very scattered across the code base and seemingly unrelated
Further, I remember discussion of using the TSDB inverted index to do this.
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
The issue names no files or tests; begin by locating the scattered alert-access maps and the code using the TSDB inverted index. Review how alert indexing and search currently work, then define a consolidated approach and its expected lookup behavior before implementation. Done should mean alert indexing and search use a coherent, documented mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, search
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100