Send downpipes alerts by email
Email sends a plain notification to one or more addresses you choose. It is a notification only: there is no incident state, so nothing here de-duplicates or auto-resolves.
What you need
- One or more destination email addresses for the alerts.
- Access to the downpipes console with the notify-config capability (Operator, Approver or Owner), and the engine’s outbound email binding configured for live sending.
Set it up
- In the downpipes console, open Notifications, choose Add a channel and pick Email. Adding a channel needs the notify-config capability, so an Operator, Approver or Owner can add one.
- Enter the destination addresses, comma-separated, give the channel a name you recognise, and save it. A rule then routes events to it.
- Choose Test on the channel row to confirm delivery without sending real alert content, then check the message arrived.
Good to know
- Live sending needs the engine’s email binding. The console accepts the channel either way, but the engine only sends when its outbound email binding is configured; without it, a delivery reports as email-not-configured rather than sending. Each alert is plain text carrying the event, severity, downpipe name and time, with a subject prefixed
[downpipe]. - Notification only. A recovery arrives as another email rather than clearing an earlier one, so pair email with an incident platform when you need dedup and auto-resolve.
Last updated .