Integration · APM & alerting
Telegram
Bot API, threading by message_id, reply chains.
What gets collected
Create a bot via @BotFather, add it to a chat, and the cabinet stores chat_id. A re-fire replies to the original message.
Requirements
- ✓Bot token (@BotFather)
- ✓chat_id
- ✓bot added to chat
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
telegram.messages.senttelegram.delivery.errorstelegram.reply.chainsSetup steps
- 1
@BotFather → /newbot - 2Add to a group / get chat_id via getUpdates
- 3Token + chat_id in the channel config
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
Telegram
Frequently asked questions
- What does Unimoni collect from Telegram?
- Bot API, threading by message_id, reply chains. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Telegram and everything else in one place.
- How long does it take to connect Telegram?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the Telegram integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is Telegram monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.