prometheus / prometheus/alertmanager
GCS file as a configuration source
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
Instead of a local file being the configuration source, we would like to see the ability to read from GCS or S3 buckets to retrieve configuration.
Use case is running a distributed service in many regions with Alertmanager configured in each VM.
Right now, we would have to redeploy the static file or write a hacky storage script to pull the file and restart Alertmanager.
It would be beneficial to just update the storage file through Terraform, Alertmanager gets the updated file from GCS, and we don't have to worry about pushing a new copy of the deployment across regions.
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 by reviewing Alertmanager's existing local-file configuration path and the deployment assumptions described in the issue. Compare the requirements for GCS and S3 retrieval, including updates across regions, refresh behavior, and failure handling. Done means the supported storage sources and configuration-update behavior are clearly defined and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, google-cloud
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100