Alert Channels
Alert channels determine how you receive notifications when monitors detect issues. PixoMonitor supports 8 different notification channels so you can get alerts wherever works best for your team.
Available Channels
| Channel | Best For | Setup Complexity |
|---|---|---|
| Personal notifications | Easy | |
| Slack | Team chat integration | Easy |
| Discord | Developer communities | Easy |
| Telegram | Mobile notifications | Medium |
| Microsoft Teams | Enterprise teams | Easy |
| SMS | Critical alerts | Easy |
| Voice | Urgent escalations | Easy |
| Webhooks | Custom integrations | Medium |
Email is the default notification channel. Alerts are sent directly to your inbox with detailed information about the incident.
Setup
Go to Alert Channels
Navigate to Settings → Alert Channels and click Add Channel.
Select Email
Choose Email as the channel type.
Enter your email address
Enter the email address where you want to receive alerts.
Save and test
Click Save, then use the Test button to verify delivery.
Email Content
Alert emails include:
- Monitor name and URL
- Current status (DOWN/UP)
- Error message (if applicable)
- Response time
- Timestamp
- Direct link to the monitor dashboard
Add alerts@pixomonitor.com to your email contacts or safe senders list to ensure alerts don't go to spam.
Slack
Send alerts to Slack channels for team visibility. Alerts appear as rich messages with status indicators and action buttons.
Setup
Create a Slack webhook
- Go to api.slack.com/apps
- Click Create New App → From scratch
- Name your app "PixoMonitor" and select your workspace
- Go to Incoming Webhooks and enable them
- Click Add New Webhook to Workspace
- Select the channel for alerts
- Copy the webhook URL
Add the channel in PixoMonitor
- Go to Settings → Alert Channels → Add Channel
- Select Slack
- Paste your webhook URL
- Click Save
Test the integration
Click the Test button to send a test alert to your Slack channel.
Slack Message Format
Alerts include:
- Color-coded status indicator (green/red/yellow)
- Monitor name and URL
- Status and error details
- "View Monitor" button linking to the dashboard
For multiple channels, create separate alert channels in PixoMonitor, each with its own Slack webhook URL.
Discord
Send alerts to Discord servers via webhooks. Perfect for developer communities and gaming-related services.
Setup
Create a Discord webhook
- Open your Discord server settings
- Go to Integrations → Webhooks
- Click New Webhook
- Name it "PixoMonitor" and select the channel
- Click Copy Webhook URL
Add the channel in PixoMonitor
- Go to Settings → Alert Channels → Add Channel
- Select Discord
- Paste the webhook URL
- Click Save
Test the integration
Click the Test button to send a test alert.
Discord Message Format
Alerts appear as embedded messages with:
- Color-coded embed (red for down, green for up)
- Monitor name as the title
- Status, URL, and error fields
- Timestamp footer
Telegram
Receive alerts via Telegram bot. Great for mobile notifications with instant delivery.
Setup
Create a Telegram bot
- Open Telegram and search for @BotFather
- Send
/newbotto create a new bot - Follow the prompts to name your bot
- Copy the bot token provided
Get your chat ID
- Start a chat with your new bot
- Send any message to the bot
- Visit
https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getUpdates - Find the
chat.idvalue in the response
For group chats, add the bot to the group first, then check getUpdates for the group chat ID (will be a negative number).
Add the channel in PixoMonitor
- Go to Settings → Alert Channels → Add Channel
- Select Telegram
- Enter your bot token and chat ID
- Click Save
Test the integration
Click the Test button to verify the bot can send messages.
Keep your bot token secret. Anyone with the token can send messages as your bot.
Microsoft Teams
Send alerts to Microsoft Teams channels using Incoming Webhooks.
Setup
Create a Teams webhook
- Open Microsoft Teams
- Navigate to the channel where you want alerts
- Click the ... menu → Connectors
- Find Incoming Webhook and click Configure
- Name it "PixoMonitor" and optionally add an icon
- Click Create and copy the webhook URL
Add the channel in PixoMonitor
- Go to Settings → Alert Channels → Add Channel
- Select Microsoft Teams
- Paste the webhook URL
- Click Save
Test the integration
Click the Test button to send a test message to your Teams channel.
Teams Message Format
Alerts appear as Message Cards with:
- Theme color based on status
- Activity title with status emoji
- Facts table with monitor details
- "View Monitor" action button
SMS
Receive text message alerts on your phone. Ideal for critical alerts that need immediate attention.
Setup
Add SMS channel
- Go to Settings → Alert Channels → Add Channel
- Select SMS
Enter your phone number
Enter your phone number in E.164 international format:
+1234567890
Include the country code with a + prefix.
Save and verify
Click Save, then use the Test button to verify delivery.
SMS Content
SMS alerts are kept brief (under 160 characters) and include:
- Monitor name
- Current status
- Timestamp
SMS alerts are rate-limited to prevent spam. There's a 5-minute cooldown between SMS alerts for the same monitor.
Voice Calls
For critical alerts, PixoMonitor can call you with a spoken message. The call will repeat the alert details twice.
Setup
Add Voice channel
- Go to Settings → Alert Channels → Add Channel
- Select Voice
Enter your phone number
Enter your phone number in E.164 international format:
+1234567890
Save
Click Save to enable voice call alerts.
Voice Alert Content
The automated call will say:
"PixoMonitor monitoring alert. Your monitor [name] is currently [status]. [Error details]. Please check your dashboard for details. Repeating: [name] is [status]."
Use voice alerts as a final escalation step in your escalation policy for critical incidents that aren't acknowledged.
Webhooks
Webhooks let you integrate PixoMonitor with any service that accepts HTTP requests. Use webhooks for custom integrations, incident management tools, or automation workflows.
Setup
Add Webhook channel
- Go to Settings → Alert Channels → Add Channel
- Select Webhook
Configure the webhook
- URL — The endpoint to receive alerts
- Secret — Optional secret for signature verification
Save and test
Click Save, then Test to verify connectivity.
Webhook Payload
Webhooks receive a JSON payload:
{
"event": "monitor.down",
"monitor": {
"id": "uuid",
"name": "My Website",
"url": "https://example.com",
"type": "HTTP"
},
"alert": {
"status": "DOWN",
"error": "Connection timeout",
"responseTime": null,
"timestamp": "2026-03-24T12:00:00Z"
}
}Event Types
| Event | Description |
|---|---|
monitor.down | Monitor detected a failure |
monitor.up | Monitor recovered |
monitor.anomaly | Performance anomaly detected |
Signature Verification
If you provide a secret, PixoMonitor signs payloads with HMAC-SHA256. Verify the signature from the X-Signature header:
const crypto = require('crypto');
function verifySignature(payload, signature, secret) {
const expected = crypto
.createHmac('sha256', secret)
.update(JSON.stringify(payload))
.digest('hex');
return crypto.timingSafeEqual(
Buffer.from(signature),
Buffer.from(expected)
);
}Webhook URLs must be publicly accessible. Private/internal IPs (10.x.x.x, 192.168.x.x, localhost) are blocked for security.
Testing Alert Channels
Every alert channel has a Test button to verify it's working correctly.
What Test Alerts Include
Test alerts are clearly marked and include sample data:
- Test monitor name
- "DOWN" status
- Message explaining it's a test
- Timestamp
Troubleshooting Test Failures
If test alerts fail:
- Email — Check spam folder, verify address
- Slack/Discord/Teams — Verify webhook URL hasn't been revoked
- Telegram — Ensure bot hasn't been blocked
- SMS/Voice — Verify phone number format (+1234567890)
- Webhooks — Check endpoint returns 2xx, verify firewall rules
Managing Multiple Channels
You can configure multiple alert channels to ensure you never miss an alert:
- Email + Slack — Personal notification plus team visibility
- SMS + Voice — Critical alerts during on-call hours
- Webhook — Integration with incident management tools
Alert Priority with Escalation Policies
Use escalation policies to configure tiered alerting:
- Immediate — Slack notification
- 5 minutes — SMS to on-call engineer
- 15 minutes — Voice call if not acknowledged
Test all your alert channels regularly, especially before relying on them for critical production services.
Best Practices
- Use multiple channels — Don't rely on a single notification method
- Test after setup — Always verify channels work before going live
- Configure escalation — Set up tiered alerts for critical services
- Keep credentials secure — Treat webhook secrets like passwords
- Monitor for spam — Configure appropriate cooldown periods
- Review regularly — Ensure channels still work and reach the right people
