Advanced
Notifications
Being told when something unattended fails, which is the only time a message is worth sending.
Notifications fire when a scheduled job or a GitOps sync fails. Those are the two systems that run with nobody watching, which is exactly when a failure can sit unnoticed.
Channels
| Channel | Notes |
|---|---|
| smtp | Real email, over a real SMTP implementation — TLS, STARTTLS and authentication have enough subtleties that hand-rolling them would have been a mistake. |
| slack | A stable JSON payload to an incoming webhook. |
| discord | The same, in Discord's shape. |
| webhook | A generic JSON POST, for anything the three above do not cover. |
Each channel has a test endpoint, so you can find out whether it is configured correctly at the moment you configure it rather than the first time something breaks.
The channel list is deliberately short. The obvious way to cover every service at once would have pulled a Python runtime into a codebase that has avoided one everywhere else; the popular subset beyond email is three simple, stable payloads instead.
Air-gapped
- An internal SMTP relay or an internal webhook receiver works normally. Slack and Discord need egress to reach their own services.