Alerts
Alert rules live in a project's Alerts tab, visible to organization owners.
Slack
Paste a Slack incoming webhook URL into the project's Slack integration settings. Once configured and enabled, any rule with Slack delivery turned on posts there.
Alert rules
A rule fires on one of three triggers:
- New issue — a brand-new fingerprint was just created.
- Regression — a previously resolved issue just reopened.
- Frequency — the issue's total event count reaches a threshold you set, firing once at that exact count (not on every event past it).
Each rule delivers to Slack, a list of emails, or both, and is throttled per issue — by default 60 minutes, configurable per rule — so a noisy issue doesn't spam the same channel every second.
Alert evaluation runs after the triggering event is fully committed to storage, so alerts never sit in the hot ingest path.
Email delivery
Email delivery requires SMTP configuration. Without it, email targets on a rule are silently skipped and Slack delivery still works normally.
| Variable | Default | Purpose |
|---|---|---|
OKAPI_SMTP_HOST |
— | Setting this enables outgoing email. |
OKAPI_SMTP_PORT |
587 |
SMTP port. |
OKAPI_SMTP_USER |
— | SMTP username (enables PLAIN auth when set). |
OKAPI_SMTP_PASSWORD |
— | SMTP password. |
OKAPI_SMTP_FROM |
okapi@localhost |
From address for outgoing alert email. |
This is the same SMTP configuration Okapi uses for invite emails, email verification, and password reset — one set of variables covers all outgoing mail.
Next: Quotas & usage.