- Routing: rules pick channels by kind, severity and server tags (first match wins, none = nobody); mixed batches split per route; recoveries follow their alert; quiet-hours digest keeps each notification's audience - Push: each subscribed browser can ask for a minimum severity and some kinds - Escalation: up to three timed steps re-notify alerts nobody has acknowledged, through chosen channels and an optional extra email; an acknowledgement stops them - Fix ntfy: titles with an em dash made every ntfy send fail (header not Latin-1); now RFC 2047 encoded Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
5 lines
397 B
SQL
5 lines
397 B
SQL
ALTER TABLE `alert_incidents` ADD `escalated_step` integer DEFAULT 0 NOT NULL;--> statement-breakpoint
|
|
ALTER TABLE `alert_incidents` ADD `escalated_at` text;--> statement-breakpoint
|
|
ALTER TABLE `notification_queue` ADD `audience` text;--> statement-breakpoint
|
|
ALTER TABLE `push_subscriptions` ADD `min_severity` text;--> statement-breakpoint
|
|
ALTER TABLE `push_subscriptions` ADD `categories` text; |