Channels & Events

Warden notifies you when monitors change state. Set up a notification channel and you’ll start receiving alerts immediately — no extra configuration needed.

Notification Channels

Warden supports two channel types:

Type	Description
Slack	Rich formatted messages via Slack Incoming Webhooks
Webhook	JSON payloads to any HTTP endpoint

All enabled channels receive every notification. You can create as many as you need.

Adding a Channel

1. Go to Settings → Notifications
2. Click Add Integration
3. Choose Slack or Webhook
4. Enter a name and your webhook URL
5. Click Send Test to verify it works
6. Click Add Integration to save

The test sends a sample “monitor down” event so you can verify formatting and delivery before saving.

Slack

Messages are color-coded by event type:

Event	Color
Down	Red
Degraded	Yellow
SSL Expiring	Orange
Flapping	Purple
Stabilized	Blue
Up (Recovery)	Green

Each message includes the monitor name, URL, event details, and timestamp.

To set up Slack, create an Incoming Webhook in your Slack workspace and paste the URL when creating the channel.

Webhook

Webhooks send a JSON POST to your endpoint with a 10-second timeout:

{
  "event": "down",
  "monitorId": "m-api-server-a1b2c3",
  "monitorName": "API Server",
  "monitorUrl": "https://api.example.com",
  "message": "Connection refused",
  "timestamp": "2026-03-20T12:00:00Z"
}

Event Types

Event	Trigger
Down	Monitor confirmed down after consecutive failures
Up	Monitor recovered
Degraded	Latency exceeded threshold
Flapping	Rapid state changes detected
Stabilized	Flapping stopped
SSL Expiring	Certificate approaching expiry (30, 14, 7, or 1 day)

Each event type can be independently enabled or disabled in Settings → Notifications → Event Types. All are enabled by default. Disabled events are still logged — they just don’t trigger notifications.

Notification Intelligence

These settings help reduce noise so you only get alerted when it matters. The defaults work well for most setups — adjust them if you’re seeing too many or too few alerts.

Confirmation Threshold

Warden waits for multiple consecutive failures before confirming a monitor is down. This filters out one-off network blips.

Default: 3 consecutive failures. Set to 1 for immediate alerting. Range: 1–100.

Notification Cooldown

After sending an alert, Warden suppresses duplicate alerts for the same event type for a cooldown period. Recovery notifications always send regardless of cooldown.

Default: 30 minutes. Set to 0 to disable. Range: 0–1440 minutes.

Recovery Confirmation

Require consecutive successful checks before confirming recovery, preventing false recovery alerts from intermittent issues.

Default: 1 check. Range: 1–20.

Flap Detection

If a monitor keeps switching between up and down, Warden detects the instability and sends a single “flapping” alert instead of repeated up/down notifications. Once the monitor stabilizes, you get a “stabilized” notification with a 5-minute grace period before it can re-trigger.

Default: Enabled, analyzing the last 21 checks with a 25% state transition threshold.

All of these settings can be changed in Settings. Confirmation threshold and cooldown can also be overridden per monitor.

Daily Digest

Instead of immediate alerts for non-critical events, batch them into a daily summary.

Setting	Default	Description
Enabled	Off	Toggle daily digest mode
Time	09:00	Delivery time in your timezone
Event Types	degraded, flapping, stabilized, ssl_expiring	Which events to batch

Events in the digest list are queued and delivered once daily. Critical events like down and up are always sent immediately regardless of digest settings.

Permissions

• Admin and Editor can create, edit, delete, and test channels
• Admin only can change notification settings (thresholds, event toggles, digest)
• Viewer can see channels (webhook URLs masked) but cannot modify them
• Status Viewer has no access to notifications