๐ข Notifications Overview
Monitron SaaS supports 19 notification channels to make sure you never miss an alert. You can use multiple channels simultaneously and configure different channels for different contacts.
๐ Available Channelsโ
๐ฌ Chat & Messagingโ
| Channel | Best For |
|---|---|
| ๐ง Email | Universal โ everyone has email |
| ๐ฌ Slack | Team channels, DevOps workflows |
| ๐ฎ Discord | Community-based teams |
| โ๏ธ Telegram | Fast personal alerts |
| ๐ฅ Microsoft Teams | Enterprise environments |
| ๐ฌ Google Chat | Google Workspace users |
๐ฑ Push Notificationsโ
| Channel | Best For |
|---|---|
| ๐ฑ Pushover | Reliable push with priority levels |
| ๐ซ Pushbullet | Cross-device push notifications |
| ๐ OneSignal | Web and mobile push |
| ๐ก Pusher Beams | Real-time push infrastructure |
| ๐ ntfy | Self-hosted push (no account needed!) |
| ๐ Gotify | Self-hosted push notifications |
๐ฒ SMS & Voiceโ
| Channel | Best For |
|---|---|
| ๐ฒ SMS via Twilio | Reliable SMS worldwide |
| ๐ฒ SMS via Vonage | Alternative SMS provider |
| ๐ Voice Call via Twilio | Critical alerts that can't be missed |
| ๐ฌ WhatsApp | WhatsApp messages via Twilio |
๐ง DevOps & Customโ
| Channel | Best For |
|---|---|
| ๐ Custom Webhook | Integrate with any service |
| ๐จ PagerDuty | Enterprise incident management |
| ๐จ OpsGenie | Atlassian incident management |
๐ง How Notifications Workโ
Architectureโ
Monitor Down
โ
โผ
Incident Created
โ
โผ
Alert Rules Evaluated
โ
โผ
Contact Groups Resolved
โ
โผ
Each Contact's Channels Dispatched
โ
โโโ Email sent
โโโ Slack webhook fired
โโโ Telegram message sent
โโโ SMS dispatched
Flow Explainedโ
- A monitor goes down โ An incident is automatically created
- Alert rules are checked โ Rules determine which contacts should be notified
- Contacts are resolved โ Each contact can have multiple channels
- Notifications are dispatched โ Each channel is sent asynchronously via queue
- Everything is logged โ Check Notification Logs for delivery status
๐ Configuration Levelsโ
Notifications are configured at two levels:
1. Global Provider Settings (Admin โ Settings โ Notification Providers)โ
These are API keys and tokens that apply to your entire Monitron installation:
- Telegram Bot Token
- Twilio SID, Token, Phone Numbers
- Vonage API credentials
- OneSignal App ID and API Key
- Pushover API Token
- etc.
2. Per-Contact Channel Settings (Contacts โ Edit Contact)โ
Each contact configures their own channel-specific settings:
- Their Slack webhook URL
- Their Telegram chat ID
- Their phone number for SMS
- Their Pushover user key
- etc.
๐ Notification Eventsโ
Monitron sends notifications for these events:
| Event | Description |
|---|---|
monitor.down | A monitor has gone down |
monitor.recovery | A monitor has recovered |
monitor.degraded | Response time exceeds threshold |
ssl.expiring | SSL certificate expiring soon |
heartbeat.missed | Heartbeat ping not received |
agent.stale | Server agent stopped reporting |
๐ก Best Practicesโ
-
Use multiple channels โ Don't rely on just email. Add a push notification (Pushover, Telegram) for faster alerts.
-
Separate critical from non-critical โ Set up different contacts/groups for critical monitors (get SMS + voice call) vs. informational ones (email only).
-
Test your channels โ After setting up, trigger a manual check on a known-down service to verify notifications arrive.
-
Check the Notification Logs โ Go to Notification Logs in the sidebar to see every notification attempt, whether it succeeded, and any error messages.