prometheus / prometheus/alertmanager
V2 Matchers don't have ability to match
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
This may be completely on me, but I cannot find anywhere where v2 Matchers have the ability to actually match anything, as compared to the old Prometheus labels matchers that were used in the v1 client.
What did you do?
Attempted to migrate v1 Golang client application to v2 and use Matchers for Silence responses.
What did you expect to see?
Matchers field within a Silence to have the ability to match regex.
What did you see instead? Under which circumstances?
V2 Matchers within Silence have no ability to match.
Environment
-
System information:
Darwin 20.6.0 x86_64
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
No files, tests, or entry points are named. Start by comparing the v1 Prometheus label matchers with the v2 Silence Matchers implementation and its API behavior. Done means v2 Silence Matchers can perform regex matching with behavior consistent with the reported v1 capability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100