Notifications & Webhooks Help

Notifications Back to Settings
Channels

Create destinations first: Slack, webhook, email, and browser push can coexist.

Rules

Define signal and tag conditions, then attach one or more channels with cooldown controls.

Checks

Rules fire when the notification check endpoint is called by schedule or manual check action.

Channels and Rules
Create channels first (Slack/webhook/email/browser push), then define rules that evaluate signal conditions and route notifications.
Condition Tips
  • Use service filters to keep alerts actionable.
  • Use cooldown windows to avoid alert storms.
  • For regex tag conditions, validate syntax before saving.
  • Prefer explicit thresholds and avoid broad all-service rules first.
Operational Runbook
  1. Create and test at least one channel.
  2. Create one rule with a narrow service scope.
  3. Run a manual check from the UI to validate end-to-end delivery.
  4. Enable periodic scheduler calls to the check endpoint.
  5. Review cooldown/noise behavior and tune thresholds.
Troubleshooting
  • If no alerts are sent, verify at least one enabled channel is attached.
  • If checks run but channels stay quiet, confirm condition windows and comparator direction.
  • If regex-based tag rules fail, re-test expression syntax and escaping.
  • If notifications spam, increase cooldown and narrow service/condition scope.
Rules are evaluated when the check endpoint runs: POST /api/notifications/check.