ErrTap docsconcepts / alerts
Alerting
Configure notification channels and alert rules for issue lifecycle, spikes, downtime, recovery, SSL expiry, and missed heartbeats.
Channels
Channels are notification destinations. ErrTap supports:
- Email — one or more addresses
- Slack — incoming webhook URL
- Generic webhook — any HTTP endpoint that accepts the alert JSON payload
Channel secrets are encrypted at rest. Use Test on any channel to verify delivery before wiring it to rules.
Alert types
| Type | When it fires |
|---|---|
NEW_ISSUE | A never-before-seen error group appears |
REGRESSED_ISSUE | A resolved issue comes back in a new release (or after a snooze expires) |
DOWNTIME | An uptime check is confirmed down |
RECOVERY | An uptime check recovers after a downtime incident |
SSL_EXPIRY | A monitored certificate crosses an expiry warning threshold |
CRON_MISSED | A heartbeat did not arrive within the grace window |
ERROR_SPIKE | Project event volume exceeds its recent baseline |
Rules
Rules bind an alert type to one or more channels. Each rule can be scoped to:
- A specific environment for
NEW_ISSUEandREGRESSED_ISSUErules
Deduplication / cooldown
Rules carry a cooldown window: ErrTap fires at most one alert per issue (or check) per window. This means an error storm pages you once — not hundreds of times.
Configure the cooldown duration per rule in Alerts → Alert rules.
Configuring rules
Navigate to Alerts → Alert rules → New rule:
- Choose an alert type
- Select one or more channels
- Optionally select an environment for an issue lifecycle rule
- Set a cooldown window (default: 5 minutes)
- Save and test