Skip to main content

Alerts

Two kinds of rules, one set of delivery targets.

Channels​

A channel is a notification target owned by the project and shared by every rule in it: email, Slack, Discord, Teams, PagerDuty, OpsGenie, a generic webhook and more. Create channels under Monitor → project → Channels before adding rules. Types, required fields and message formats are on Notification channels.

Uptime alert rules​

Uptime rules belong to a monitor and fire after N consecutive failed checks (default 3). Dashboard: the Alert rules section on the monitor page, which picks one of the project's channels. CLI:

kamu status alerts list <monitor-id>
kamu status alerts add <monitor-id> --type email --target ops@example.com --consecutive 3
kamu status alerts add <monitor-id> --type slack --target https://hooks.slack.com/services/...
kamu status alerts add <monitor-id> --type webhook --target https://example.com/alerts
kamu status alerts delete <alert-id>

kamu status alerts add takes an inline --type (email, slack or webhook) and --target instead of a channel.

While a monitor stays down, a rule notifies again every 10 minutes. A recovery sends one UP message. During a maintenance window alerts for the linked monitors are suppressed (heartbeat monitors still alert).

HTTPS monitors also send certificate and domain expiry warnings through the same rules (see monitor types).

A heartbeat monitor alerts when no ping arrives within its expected period plus grace; the same rules apply, without the consecutive-failure count. See heartbeats.

Error alert rules​

Per property, on the property's Alert rules tab:

  • new_group — a never-before-seen error appears.
  • error_rate — share of sessions hitting an error crosses a threshold (floored at 10 sessions/window so quiet hours don't false-positive).
  • group_regression — a resolved group reappears (the group is reopened).

Rules deliver through the project's channels, shared with uptime alerts.

Error alert rules are not in the kamu CLI. Use the dashboard or the API.

Webhook payload​

Webhook channels receive a small JSON object (monitor, monitorId, status, error, region, timestamp, plus property fields for error alerts). The exact shape is on Notification channels.