Skip to main content

Creating Alert Policies

Alert policies define how notifications are triggered and where they are sent.

Policies are created and managed from within a monitor.

Opening Alert Policies​

  1. Navigate to Monitors
  2. Select a monitor
  3. Click the Alert Policies tab
  4. Click Add Alert Policy

A panel will open to create a new policy.

Configuration Fields​

Name​

A descriptive name for the alert policy.

Example:

  • Primary Email Alerts
  • Webhook - Incident Notifications

Channel​

Select how alerts will be delivered:

  • Email
  • Webhook

Destination​

Where alerts are sent.

  • For Email: enter an email address
  • For Webhook: enter a URL endpoint

Min Failures​

The number of consecutive failures required before triggering an alert.

Example:

  • 1 — Alert immediately
  • 2+ — Reduce false positives

Cooldown (seconds)​

The amount of time to wait before sending another alert.

Example:

  • 900 = 15 minutes

This prevents alert flooding during ongoing incidents.

Enabled​

Controls whether the alert policy is active.

  • Enabled ✅ — Alerts will be sent
  • Disabled ❌ — Alerts are paused

How Alerts Trigger​

Alerts are sent when:

  • A monitor fails repeatedly (based on Min Failures)
  • The alert policy is enabled
  • The cooldown period has passed

Editing a Policy​

From the Alert Policies list:

  • Click Edit to update settings
  • Changes take effect immediately

Deleting a Policy​

Click Delete to remove the policy.

⚠️ This will stop alerts for any monitors using this policy.

Best Practices​

  • Use at least 2 failures to avoid false positives
  • Set cooldowns to prevent alert fatigue
  • Use multiple policies for redundancy (e.g., Email + Webhook)
  • Regularly review delivery logs

A common configuration:

  • Email alert (Min failures: 2, Cooldown: 15 minutes)
  • Webhook alert (Min failures: 2, Cooldown: 5 minutes)