Send analysis results via email to one or more recipients
The Email channel sends analysis results to a list of recipients. We handle delivery on our end — nothing to install or configure on the email side. Email is the simplest channel for stakeholders who don't live in chat: managers, security teams, on-call rotations using PagerDuty for routing.
You configure a list of recipient emails per channel and we handle delivery from our end. Nothing to install or configure on the email side.
Setup walkthrough
Add the channel in SigSentry
In the dashboard, Project → Channels → Add Channel.
| Field | Value |
|---|---|
| Type | |
| Name | Descriptive label, e.g. oncall-rotation |
| Recipients | Comma-separated list of emails |
| Severity threshold | Lowest severity to trigger this channel |
Save and test
Click Save. Run a test analysis to verify recipients receive email.
What gets sent
Each email includes:
- A severity prefix in the subject line (e.g.
[HIGH] Checkout API returning 500s) - The analysis summary, root cause, affected services, and suggested actions
- A link back to the full analysis in the dashboard
Every recipient on the channel receives the same email. There's no per-recipient templating.
Recipient management
Recipients are a comma-separated list. You can update them anytime by editing the channel — changes take effect on the next notification.
For larger rotations, consider:
- A shared mailing list (e.g.
oncall@company.com) — one entry on the SigSentry side, your DL handles routing - Multiple email channels per project, with different severity
thresholds —
oncall-critical(threshold: critical) plusengineering-summary(threshold: high)
Deliverability
Email delivery is generally reliable, but watch for:
- Bounces — invalid addresses are logged as failed deliveries and not retried
- Spam filtering — corporate filters may flag automated alerts.
Add SigSentry's
fromaddress to allowlists if you see drops
Troubleshooting
| Symptom | Likely cause |
|---|---|
| No email arrives | Spam folder, or recipient address invalid (check delivery log) |
| Some recipients receive but not others | Address-specific issue (typo, blocked domain, full mailbox) |
| Email is plain text only | Recipient's client stripped HTML; both formats are sent |
| Slow delivery | Provider rate-limited; deliveries retry with backoff |