Events

Every service writes events in the same transaction as the change and delivers them to notify with retries. Subscribe to them in notify (Notifications); home's Activity shows them all.

Service	Events
pages	`deploy.created`, `deploy.failed`, `deploy.expired`, `domain.verified`, `domain.lost`
apps	`app.deployed`, `app.deploy_failed`, `app.crashed`, `app.recovered`, `cron.failed`, `bot.webhook_failed`, `node.online`, `node.offline`, `quota.near_limit`, `database.backup_failed`, `database.restored`
env	`env.changed` (names only)
domains	`domain.attached`, `domain.detached`, `zone.delegated`, `zone.signed`, `zone.dnssec_mismatch`, `zone.unreachable`, `nameserver.stale`
backups	`backup.succeeded`, `backup.failed`, `backup.verify_failed`, `restore.finished`
status	`monitor.down`, `monitor.up`, `monitor.degraded`, `heartbeat.missed`, `certificate.expiring`, `incident.opened`, `incident.resolved`
errors	`issue.new`, `issue.regressed`, `issue.spike`
id	`user.created`, `user.disabled`, `team.member_added`, `team.member_removed`, `token.created`, `token.revoked`
topics	whatever scripts post, with the priority they choose

Severity

Events are info, warning or critical. Subscriptions take a minimum severity; quiet hours hold everything below critical. Topic posts map --priority high to warning and urgent to critical.

Webhook deliveries

A webhook channel receives each event as JSON with an HMAC-SHA256 signature of the body in X-Xvii-Signature, using the channel's secret. Check the signature, and treat deliveries as at least once: the event's id makes repeats recognisable.

From the CLI

xvii notify events --type 'app.*' -n 50
xvii notify events --severity critical --json