Notification Channels Overview
Notification channels are the destinations where PingSLA sends incident alerts and recovery notifications.
Available Channels
| Channel | Setup Complexity | Best For |
|---|---|---|
| Email → | None | All teams |
| Telegram → | Low | Small teams, mobile alerts |
| Slack → | Medium | Teams already using Slack |
| Webhook → | Medium–High | Custom integrations, PagerDuty, OpsGenie |
Channel vs Policy
A notification channel is the destination (e.g., an email address or Slack workspace).
An alert policy is the rule that determines when to fire a notification.
Channels are reusable — you can attach the same Telegram group to multiple alert policies.
Managing Channels
Go to Settings → Notification Channels to:
- Create channels
- Test channels (sends a test notification)
- Edit channel configuration
- Delete channels
Notification Payload
All incident notifications include:
- Monitor name and URL
- Incident type (DOWN / RECOVERED)
- Failure reason (status code, timeout, keyword mismatch)
- Time of detection
- Direct link to the incident in the dashboard
Delivery Guarantees
PingSLA retries failed notification deliveries up to 3 times with exponential backoff (30s, 120s, 480s).
If all retries fail, the delivery failure is recorded in the incident timeline. You can manually re-trigger notifications from the incident detail page.