Skip to content
downpipes docs

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 permission to configure notifications (Operator, Approver or Owner), and the engine’s outbound email binding and its sender address (EMAIL_FROM) configured for live sending.

Set it up

  1. In the downpipes console, open Notifications, choose Add a channel and pick Email. Adding a channel needs permission to configure notifications, so an Operator, Approver or Owner can add one.
  2. Enter the destination addresses, comma-separated, give the channel a name you recognise, and save it. A rule then routes events to it.
  3. 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 and sender address. The console accepts the channel either way, but the engine only sends when its outbound email binding and EMAIL_FROM are configured. Without the binding, a delivery reports as email-not-configured. Without EMAIL_FROM, it reports as email-from-not-configured. Each alert has a plain-text part and an HTML part, with a subject prefixed [downpipe]. Both parts carry a one-line detail, the event, the severity, the downpipe name (when the event has one) and the time.
  • 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 .