Which alert channel should I use?
Use PagerDuty for on-call rotations, Slack or Teams for daytime triage, Telegram or ntfy for solo owners, and webhooks for custom pipelines.
Quick answer#
Match the channel to the response pattern: PagerDuty for wake-me-up rotations, Slack/Teams/Discord for team triage during working hours, Telegram/ntfy for solo owners, and webhooks for custom automation.
Recommended by team size#
Where to find it in Lemwatch#
Settings → Integrations — each channel has its own routing rules.
FAQ#
Should I add all channels?#
No — alert fatigue is real. Start with one primary and one fallback.
Can I quiet a channel overnight?#
Yes — quiet hours per channel in alert rules.
Related#
Related Articles
What integrations does Lemwatch support?
Lemwatch routes alerts to Slack, Discord, Teams, PagerDuty, Telegram, Google Chat, Mattermost, Rocket.Chat, ntfy, generic webhooks, and email.
How do I test an integration is working?
Every integration has a Send Test button that fires a synthetic incident payload to the channel and confirms delivery in the UI.
PagerDuty Integration
Route critical alerts to PagerDuty for on-call incident management.
MCP security model and role scopes
MCP tokens inherit the calling member's role, further clamped by an optional role override. Writes require confirm. Admin actions require admin.