prometheus / prometheus/alertmanager
Alertmanager does not read telegram token file until there is an alert to send.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
I had an outage last night and did not get an alert because:
Jul 17 08:15:03 nixos alertmanager[233766]: time=2025-07-17T08:15:03.711Z level=ERROR source=dispatch.go:360 msg="Notify for alerts failed" component=dispatcher num_alerts=2 err="telegram/telegram[0]: notify retry canceled after 11 attempts: could not read /run/agenix/telegram-bot-token: open /run/agenix/telegram-bot-token: permission denied"
Alertmanager could try to read that file when starting instead of when there is an alert to send.
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 at the notification failure reported from dispatch.go:360 and trace how the Telegram token file is accessed and initialized. Confirm the token is read during Alertmanager startup rather than only when an alert is sent, and verify the startup behavior with the relevant notification tests or a focused reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100