Setting Up Alerts

Configure 11 notification channels — email, push, chat, on-call, and automation tools.

Setting Up Alerts

LemWatch ships 11 notification channels. Configure global defaults in Settings → Notifications, then override per site if needed. See Default vs per-site channels for the precedence rules.

Email & Push (All Plans)

• Email — Enabled by default. Customise event types, digest frequency, and quiet hours in Settings → Notifications.
• Browser Push — Instant OS notifications even when LemWatch isn't open. See Browser Push Notifications.

Chat & Team Channels (Pro+)

• Slack — Incoming webhook with rich attachments. Setup
• Microsoft Teams — Workflows (Adaptive Cards) or legacy O365 connector. Setup
• Discord — Colour-coded embeds. Setup
• Telegram — Your own bot via @BotFather. Setup
• Google Chat — Space webhook. Setup
• Mattermost — Slack-compatible incoming webhook. Setup
• Rocket.Chat — Incoming integration. Setup
• ntfy.sh — Push to phone or desktop, self-hosted friendly. Setup

On-call & Automation

• PagerDuty — Events API v2 with auto-resolve. Setup (Agency)
• Generic Webhook — JSON POST to any HTTPS endpoint. Setup
• Zapier / Make / n8n / IFTTT / Pipedream — Route alerts into any of 5,000+ apps through the Mattermost field. Recipes
• RSS — Subscribe to alerts as a feed. Setup

Alert Severity

• Critical 🔴 — Site down, security vulnerability, SSL expired (never suppressed)
• Warning 🟡 — Performance degradation, approaching limits
• Info 🔵 — SSL renewal, check completed, maintenance ended

Best Practices

1. Set up at least two channels (e.g., email + Slack) for redundancy.
2. Use quiet hours to prevent alert fatigue.
3. Configure consecutive failure thresholds to avoid false positives.
4. Route critical alerts to PagerDuty for on-call teams (Agency).
5. Use the Send test button under each channel to verify before going live.