Alert Policies

Alert policies let you route specific alert types to specific channels with custom escalation rules.

Default policy

Out of the box, all alert types go to all configured channels. You can override this with custom policies.

Custom policy example

Policy: "Critical production alerts → PagerDuty + Slack #incidents"

Conditions:
  severity = critical
  resource tag includes: env=production

Actions:
  → Slack #incidents (immediately)
  → PagerDuty (after 2 min if unacknowledged)
  → Email [email protected] (after 5 min if unacknowledged)

Escalation:
  If unacknowledged for 15 min → Slack #engineering-leads

Escalation

Configure escalation chains:

Step	Trigger	Action
1	Alert fires	Notify primary channel
2	Alert unacknowledged for 5 min	Notify secondary channel
3	Alert unacknowledged for 15 min	Page on-call via PagerDuty/OpsGenie
4	Alert unacknowledged for 30 min	Notify manager channel

Alert deduplication

SecureCheap deduplicates alerts based on:

Same resource
Same check type
Same failure reason

A second failure on the same monitor within 5 minutes does not create a second alert — it extends the duration of the existing one.

Quiet hours

Define hours when non-critical alerts are suppressed:

Quiet hours: 23:00 – 07:00 local timezone
Suppress: warning, info
Allow through: critical

Notification Channels Overview