prometheus / prometheus/alertmanager
Variable Substitution in configuration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
The topic was already addresses 8 years ago Support for secrets set in ENV variables
As already mentioned in the original issue, this is a feature supported by many other tools, including prometheus, snmp-exporter, ...
It seems that the contributor was completely missing the point of the proposal and got stuck on "Alertmanager is not a CM" which was never the subject. The request is to make alertmanager's configuration work like other configuration of prometheus stack.
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 reviewing issue #504 and the existing Alertmanager configuration handling. Done would mean defining and implementing environment-variable substitution for Alertmanager configuration, with behavior aligned to the Prometheus stack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100