Notifications

Set up multi-channel alerts for your monitors

Overview

Telemetry.host supports 50+ notification channels via Apprise integration. This guide shows you how to configure different channels and best practices for alerting.

Email Notifications

Email notifications are enabled by default for your account. All monitors will send alerts to your registered email address.

Configuring Email

  1. Go to your monitor settings
  2. Under “Notifications”, email is pre-configured
  3. Customize notification preferences (failures only, recoveries, etc.)

Discord Notifications

Step 1: Create Discord Webhook

  1. Open Discord server settings
  2. Go to Integrations → Webhooks
  3. Click “New Webhook”
  4. Copy the webhook URL

Step 2: Add to Monitor

  1. Go to monitor settings → Notifications
  2. Click “Add Channel”
  3. Select “Discord”
  4. Paste webhook URL
  5. Test notification

Discord URL Format

https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN

Or use Apprise format:

discord://YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN

Slack Notifications

Incoming Webhook

  1. Create Slack app in your workspace
  2. Enable Incoming Webhooks
  3. Create webhook for channel
  4. Add to Telemetry.host:
https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXX

Apprise Format

slack://TokenA/TokenB/TokenC

Telegram

  1. Create bot with @BotFather
  2. Get bot token
  3. Get your chat ID
  4. Add to monitor:
tgram://BOT_TOKEN/CHAT_ID

Microsoft Teams

  1. Configure Incoming Webhook in Teams channel
  2. Add webhook URL to monitor
https://outlook.office.com/webhook/...

PagerDuty

pagerduty://integration_key@routing_key

Webhook (Generic)

For custom integrations:

# POST request to your endpoint
webhook://your-domain.com/path

The webhook receives:

{
  "monitor": {
    "id": "abc123",
    "name": "Daily Backup",
    "status": "down"
  },
  "message": "Monitor has missed expected check-in",
  "timestamp": "2025-01-15T10:30:00Z"
}

Testing Notifications

Always test your notification channels:

  1. Go to monitor settings
  2. Click “Test Notification”
  3. Check that you receive the test message
  4. Adjust settings if needed

Notification Preferences

When to Send

  • Failures only: Alert when monitor goes down
  • Failures and recoveries: Alert on both state changes
  • All events: Include successful check-ins (noisy)

Notification Throttling

Prevent alert fatigue:

  • First alert: Immediate
  • Subsequent alerts: Every 4 hours while down
  • Recovery: Immediate

Multiple Channels

Add multiple channels for redundancy:

  1. Primary: Email
  2. Secondary: Discord
  3. Critical: PagerDuty

Configure per monitor based on criticality.

Best Practices

1. Test Before Deploying

Always test notifications before relying on them.

2. Use Different Channels for Different Severity

  • Info: Email
  • Warning: Discord/Slack
  • Critical: PagerDuty/Phone

3. Set Up Redundancy

Don’t rely on a single channel - email servers go down too.

4. Configure Quiet Hours

For non-critical monitors, use quiet hours to avoid nighttime alerts.

5. Group Notifications

Use team channels rather than individual DMs for shared responsibility.

Troubleshooting

Not Receiving Notifications

Check:

  • Test notification works
  • Webhook URL is correct and active
  • Email not in spam folder
  • Discord/Slack bot has channel permissions

Too Many Notifications

Solutions:

  • Adjust notification preferences to “failures only”
  • Increase monitor timeout to reduce false positives
  • Use notification throttling

Delayed Notifications

Notifications are typically sent within 30 seconds of detection. Delays usually indicate:

  • Network issues
  • Third-party service delays (Discord, Slack, etc.)

Next Steps