Pipe Alertmanager alerts into Telegram
Prometheus + Alertmanager only ship alerts to email or PagerDuty. The team lives in Telegram and you need a bridge without spinning up another service.
Recipe
# alertmanager.yml — Telegram receiver via the official telegram_configs.
# Bot token from @BotFather, chat_id from getUpdates after /start in the chat.
route:
group_by: ['alertname']
receiver: 'telegram-default'
routes:
- matchers: [severity="critical"]
receiver: 'telegram-oncall'
receivers:
- name: 'telegram-default'
telegram_configs:
- bot_token: '<BOT_TOKEN>'
chat_id: -1001234567890
parse_mode: 'HTML'
message: '{{ .CommonAnnotations.summary }}'
- name: 'telegram-oncall'
telegram_configs:
- bot_token: '<BOT_TOKEN>'
chat_id: -1001111222333
parse_mode: 'HTML'Same thing in Enterno.io
If you do not need full Prometheus yet, point a URL at an Enterno monitor — the Telegram bot links with a single /link command. No alertmanager, no webhook server.
Related recipes
An alertmanager alert sits in state=pending past its for-window — it should be active but is not firing (group_wait too big? notifier broken? misconfigured route?). Nobody gets paged.
Prometheus itself is alive, but one of its targets has up==0 — data stops flowing, graphs go blank, and alertmanager rules built on that target don't fire (no data = no alert).
Ensure your site returns 2xx every minute, alert to Slack/Telegram on failure.