DevOps teams routing critical alerts to PagerDuty and non-critical to Slack
Benachrichtigungen
Werden Sie benachrichtigt, wo Sie bereits arbeiten.
Configure alerts to reach your team through email, Slack, Discord, Telegram, webhooks, and more. Set quiet hours so you're not woken up for non-critical issues.
So funktioniert's
Choose your alert channels — email, Slack, Discord, Telegram, webhook, or PagerDuty
Set which monitors trigger which channels
Configure quiet hours to suppress alerts during maintenance windows
Set escalation thresholds — only alert after N consecutive failures
Anwendungsfälle
Solo developers getting email alerts with quiet hours set for sleep time
Häufig gestellte Fragen
What alert channels do you support?
Email, Slack, Discord, Telegram, Microsoft Teams, PagerDuty, Pushover, Google Chat, and generic webhooks. 1 channel on Free, 5 on Solo, 20 on Team.
Can I set quiet hours?
Yes — configure per-monitor quiet hours so alerts are suppressed during your maintenance windows or off-hours.
What is alert escalation?
You can set a threshold (e.g., 3 consecutive failures) before an alert fires. This prevents false alarms from transient network blips.