📢 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

Canal	Ideal Para
📧 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

Canal	Ideal Para
📱 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

Canal	Ideal Para
📲 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

Canal	Ideal Para
🌐 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

1. A monitor goes down → An incident is automatically created
2. Alert rules are checked → Rules determine which contacts should be notified
3. Contacts are resolved → Each contact can have multiple channels
4. Notifications are dispatched → Each channel is sent asynchronously via queue
5. 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:

Evento	Descripcion
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

1. Use multiple channels — Don't rely on just email. Add a push notification (Pushover, Telegram) for faster alerts.

2. Separate critical from non-critical — Set up different contacts/groups for critical monitors (get SMS + voice call) vs. informational ones (email only).

3. Test your channels — After setting up, trigger a manual check on a known-down service to verify notifications arrive.

4. Check the Notification Logs — Go to Notification Logs in the sidebar to see every notification attempt, whether it succeeded, and any error messages.