Notifications
SiroPing sends alerts to your team over Email, Telegram and Webhook when incidents open, resolve, or escalate. Channels are configured per workspace.
Configure a channel
Settings → Notifications:
- Email — the SMTP server is set in
.env(EMAIL_HOST,EMAIL_HOST_USER,EMAIL_HOST_PASSWORD,DEFAULT_FROM_EMAIL). Notification emails list the recipient addresses. - Telegram — enter the bot token and chat id. The token is encrypted at rest.
- Webhook — a POST URL that receives the incident payload (great for Slack/Teams/Zapier or your own alerting).
[!TIP] Webhook is the most flexible channel — it can talk to anything that accepts HTTP.
Test it
Every channel page has Test notification — send a sample alert and confirm it arrives before you rely on it.
Alert payload (webhook)
Each alert is a JSON POST with monitor/incident context:
{
"event": "incident_open",
"monitor": "Client A - main site",
"status": "down",
"reason": "http:500",
"incident_id": 42,
"url": "https://example.com",
"workspace": "Client A"
}
Troubleshooting
| Symptom | Check |
|---|---|
| Email never arrives | manage.py doctor → SMTP status; server IP needs SPF/DKIM? |
| Telegram silent | bot token + chat id correct? Is the bot in the chat? |
| Webhook 4xx/5xx | Check the receiver's logs; payload format above |
See Doctor for the SMTP check.