Feature

Alerts across channels

An alert is only useful where you already are, which is why it goes to your chat rather than to a dashboard nobody has open.

What it does

When an incident opens, the notification goes out to the channels you configured — Slack, Discord, PagerDuty or a webhook of your own, live today with nothing to arrange on our side.

Being honest about the exceptions: Telegram delivery is built but switches on once a bot token is set on the server; e-mail is configured and sending. We would rather say that than list a channel that silently does nothing.

An alert nobody reads is the failure mode this is designed around, so an incident that stays unacknowledged escalates instead of sitting quietly in a queue. Maintenance windows suppress the noise you expected, so planned work does not teach anyone to ignore alerts.

  • Slack, Discord, PagerDuty and custom webhooks — live today
  • E-mail and Telegram, pending provider accounts
  • Escalation when an incident goes unacknowledged
  • Maintenance windows that suppress expected noise
  • Per-channel delivery logs, so a missing alert can be traced

FAQ

About alerts across channels

Which channels work right now?

Slack, Discord, PagerDuty and your own webhooks, with nothing to configure on our side. E-mail and Telegram are built but wait on provider accounts.

What stops alert fatigue during planned work?

Maintenance windows. Schedule one and the expected noise is suppressed for its duration, so real alerts keep their meaning.

What happens if nobody acknowledges an alert?

It escalates. An unacknowledged incident is treated as unseen rather than handled.