Telegram Monitoring Alerts Setup: A Step-by-Step Guide
Short answer. Telegram is the fastest alert channel: you learn about a site outage within seconds, right in the messenger. In enterno.io linking takes a minute — start the bot, link your account with /link, enable notifications on a monitor, and you receive messages about outages, recovery and SSL expiry with inline buttons for quick navigation.
Why Telegram, not just email
- Speed: the push arrives instantly, without mail-queue delays;
- Visibility: an alert is harder to miss than an email among dozens of others;
- One-tap action: inline buttons lead to the status page, SSL check and dashboard;
- Team access: alerts can be routed to the on-call shift's group chat.
Email is great for reports, Telegram for incidents. When a site goes down, seconds matter, not "I'll check mail later."
Step 1. Start the bot and link your account
Open the enterno.io Telegram bot and press Start. Then link your account with the /link command — the bot asks you to confirm the link (email + code) so alerts reach the right person.
- Press
/startin the bot; - send
/linkand follow the prompt (email + code); - wait for the successful-link confirmation.
Step 2. Enable Telegram notifications on a monitor
Go to the monitors page, open a monitor and enable Telegram notifications. Now on a status change (down/up) and on SSL warnings you receive a message.
What you will receive
| Event | When it arrives | Message contents |
|---|---|---|
| Site down | after the failure threshold | URL, cause, time |
| Site recovered | on first successful check | URL, downtime duration |
| SSL expiring | 14 days ahead | domain, expiry date |
| SSL critical | 3 days ahead | domain, urgency |
Messages include inline buttons: open the public status page, run an SSL check and open the dashboard — you can respond straight from the chat.
Useful bot commands
/start— start the bot;/link— link your enterno.io account;/status— current status of your monitors;/monitors— list of monitors;/check— quick URL check;/unlink— unlink the account;/help— command reference.
Alternative: HMAC-signed webhook
If you need integration with your own system, use a webhook instead of (or alongside) Telegram. enterno.io signs outgoing webhooks with an HMAC signature — the receiver verifies authenticity and event time. Verification pseudocode:
# on the receiver side (signature verification pseudocode)
ts = request.header("X-Enterno-Timestamp")
sig = request.header("X-Enterno-Signature-V2") # format: sha256=...
body = request.raw_body
expected = "sha256=" + hmac_sha256(secret, ts + "." + body)
# reject stale or forged events
if abs(now() - ts) > 300: reject("stale")
if not constant_time_equals(sig, expected): reject("bad signature")Telegram is for people, webhooks are for systems. They are often used together: on-call sees the Telegram alert while incident management creates a ticket via webhook.
Other alert channels
Besides Telegram, enterno.io can send alerts to Slack, email, webhook, plus PagerDuty and Jira — pick channels to fit your team's process.
FAQ
How do I link my account to the bot?
Press /start, send /link and confirm the link (email + code). Then enable Telegram notifications on a monitor.
Can I send alerts to a group chat?
Yes, alerts can be routed to the on-call shift's chat so the whole team sees them.
What if alerts stopped arriving?
Check that the bot is not stopped and the account is linked (/status). If needed, reconnect via /unlink and /link.
Why is a webhook better than Telegram?
Webhooks are for integration with your systems (tickets, on-call). They are HMAC-signed so you can verify authenticity. Telegram is for instant notifications to people.
Connect Telegram alerts in a minute: create a monitor on enterno.io, enable Telegram notifications and link the bot with /link. Related: availability from Russia, cron monitoring via Heartbeat.