prometheus / prometheus/alertmanager
Feature request: support read configuration from http endpoint
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
In a large team, maintaining the config file for alert manger can be challenging, so many receivers and route rules.
We have a idea, to build a http service exposing APIs for different team members to read and update their config, the service also expose the whole configuration content in an endpoint, which can be read by alert manger
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, tests, or entry points to start from. Begin by clarifying the HTTP API's read and update scope, configuration ownership, and how Alertmanager would consume the exposed configuration. Done would require an agreed design and implementation criteria before coding can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100