Alerts

Overview

Alerts watch your snapshot stream and notify you the moment something meaningful changes. Instead of manually checking dashboards, you configure rules once and the platform surfaces the events that matter.

Alerts are built on two pieces:

1. Alert rules — the conditions you define (see Alert Rules)
2. Alert history — the record of every time a rule fired, shown on this page

The Alerts page

Open Alerts from the sidebar. You'll see:

• Unread count at the top, matching the badge in the sidebar
• Alert feed — a chronological list of every triggered alert
• Filters — by rule, by severity (info / warning / critical), by time range, or by read/unread status
• Mark as read — click any alert to mark it read; the sidebar badge updates

Each alert card shows:

Notification channels

When a rule fires, alerts can be delivered to:

• In-app feed (always on) — shows up on this page and in the header bell icon
• Email — sent to the user who owns the rule, if email notifications are enabled for your plan
• Webhook — fire-and-forget HTTP POST to any URL, with HMAC-SHA256 signing. See Webhooks
• Slack — via the Slack connector. See Connectors

Plan gates: Email notifications and webhooks are available on Starter and above. Slack is Professional and above.

Best practices

• Start with a few high-signal rules. Begin with 2-3 critical rules (e.g., "visibility drops by more than 20%") and add more as you learn what matters.
• Use severity deliberately. Reserve critical for things that need same-day action. Otherwise use warning or info.
• Acknowledge alerts promptly. Unread counts pile up and dilute the value of the system. Triage at least weekly.
• Route critical alerts to a shared channel. Email to one person is a single point of failure — use webhooks or Slack for team visibility.

Related docs

• Alert Rules — how to configure the conditions that trigger alerts
• Webhooks — deliver alerts to any HTTP endpoint
• Connectors — Slack, Zapier, and other outbound integrations