Alert catalog
Each entry below documents a single publisher: what triggers it, where the code lives, and the exact payload it emits. Priorities and tags travel with the message — never baked into the topic name.
WIP
Catalog is being populated
The first publisher in flight is vmon-alert-brevo.py
(VoIPMonitor alerting → topic vaspian). Engineering notes for
each alert live in the /Users/chris/src/ntfy repo under
<topic>/<rule>.md; this page will surface the curated
version once those notes are filled in.
Schema for each alert
Every alert documents the minimum needed to recreate or debug it. Runbooks, history, and ownership stay in the system that fires the alert.
- Topic
- The ntfy topic this alert publishes to
- Priority
- 1–5 — urgency, encoded per message, not in the topic name
- Tags
- CSV of short codes (e.g.
warning,rotating_light) - Trigger
- Exact condition that fires (threshold, schedule, event)
- Publisher
- Where the publishing code lives — host, repo, file:line
- Payload
- Example title, body, click target, actions as they appear on device