Features · Alerts

Smart alerting.

Threshold rules and pattern rules. Slack, email, webhook channels. PagerDuty, Teams, SMS on the roadmap. Configure in YAML or in the dashboard — YAML wins when both exist.

Two kinds of rules

  • Threshold — fire when a count or rate of matching events crosses a number in a time window. Evaluated every minute.
  • Pattern — fire on a specific event-property pattern (new fingerprint, regression, quota burn). Evaluated instantly via pub/sub.

Channels live today

  • Slack — incoming webhook, block-kit body, link back to the dashboard issue.
  • Email — Resend-backed, configurable subject, list of recipients.
  • Generic webhook — POST with HMAC-SHA256 signature, custom headers, retry with exponential backoff.

Channels on roadmap

  • PagerDuty — Events API v2.
  • Microsoft Teams — incoming webhook.
  • SMS — Twilio-backed, on-call rotation aware.

Useful default rules

  • level:fatal env:production count > 0 in 1m — page on first fatal in prod.
  • fingerprint:new env:production — new error class shows up in prod.
  • level:error rate > baseline * 5 in 5m — error rate spikes 5x baseline.
  • fingerprint.was_resolved == true — regression of a previously-fixed fingerprint.
  • project.quota_remaining_pct < 20 in 24h — close to quota.

Cooldowns and group_by

Cooldown prevents storms — after a rule fires, it won't fire again for the same group within the cooldown window (default 5 minutes). group_by: [project] means one alert per matching project, not one alert for the whole portfolio.

Acknowledge from Slack

Slack alerts include "Ack" and "Resolve" buttons. Clicking either updates the issue state in CodeRadar and quiets future alerts on that fingerprint until the next state transition.

Read more

Full alerting reference — rule syntax, channel configuration, webhook payload, thresholds.