Slack
Incoming webhook per channel. Schema digest, schedule run failure, agent offline. Click through to the workspace.
Slack setup
Optional · Alerts
When you want to be paged, not when you do not.
Documentation updates are not noisy by default. Alerts are an opt-in layer for the events you actually want to know about: a likely breaking schema change, a failed scheduled export, an agent that went offline.
Transactional email to a list of recipients. Same digest content, formatted for inbox preview and accessibility.
Email formatDelivery log
Every alert attempt is tracked with channel, status, retry count, last error, and next attempt time.
Schedule deliveryRules
Match the event. Hit the right channel.
A rule pairs a trigger with a destination. Triggers can be schema severity, scheduled run status, or agent health. Destinations are channels. Multiple rules can fire on the same event.
Schema severity
Info, Attention, or Likely breaking. Pick the threshold that wakes the on-call.
Object-type filter
Include or exclude tables, columns, indexes, views, routines, foreign keys.
Schedule failures
A scheduled export failed three times in a row. Surface it.
Agent offline
The agent missed the scheduled scan or has been disconnected for too long.
Reliability
Retry, audit, prove.
Every dispatch is a row. If the channel is down, the cloud retries with exponential backoff. The delivery log shows status, attempts, last error, and the next attempt time.
Exponential backoff
Up to six attempts with growing delays.
Per-attempt audit
Timestamp, channel, status, attempt counter, last error.
Same event shape
Retries keep the same event details so Slack and email recipients see a predictable alert every time.
FAQ
Optional alerts on schema and schedule events
Are alerts on by default? +
No. Documentation updates do not generate alerts. Subscribe explicitly when you want to be paged on schema severity, schedule failures, or agent health.
Can I notify both Slack and email? +
Yes. Create two rules with the same trigger and different destinations, or use separate rules for different severities.
Can I send the same event to two channels? +
Yes. Create two rules with the same trigger and different destinations.
Wire it up
Pick a channel. Page only on the events that matter.
Slack or email. Severity threshold and filters per rule. Retried and audited.