Overview
Email integration turns emails sent to a service's address into incidents. Use it for tools that cannot send webhooks. The email subject becomes the title and the body becomes the description.
Set it up
- In the service, click Add or Update Email Integration.
- Enter the From Email: the address your tool sends from. SQIBS sends it a code; enter it to verify. Only mail from a verified sender is processed.
- Add one or more Email Filters (up to 10), each with a Priority, Subject contains and Body contains (below).
- Save. The service info shows the address to send to (Send your emails to). Add it as a recipient in your tool.
How email filters work
- All words in Subject contains must be in the subject, and all words in Body contains must be in the body (AND), case-insensitive.
- Leave a field empty to skip that check. With both empty, every email from the sender matches.
- Up to 10 words per field, each up to 50 characters.
- Filters are alternatives (OR), tried in the order created; the first match is used.
Changes can take up to 10 minutes to apply. Titles are capped at 5000 characters and descriptions at 10000.
Debugging
Turn on Debug in the email integration to save incoming mail in the email log. It switches itself off after 48 hours.
Fix known issues automatically
Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, an email filter for backup failure messages can run a workflow that retries the backup job.
Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.
To set it up, in the same API filter:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.
Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.
Learn more:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.