Set up alerts
Ivy sends a Slack message when an error group is first seen, and a weekly email digest per workspace. Both cover failures outside the handler as well as handler errors.
Slack
- In the dashboard, open your project's alert settings and click Add to Slack.
- Approve the Slack app and pick the channel to post to.
- That's it. When a new error group appears, Ivy posts it with a View in Ivy link.
When Ivy posts. The first occurrence of a new error group posts right away. After that, the same group posts again at most every 60 minutes or every 100 occurrences, whichever comes first. You can change both thresholds per project.
What Ivy posts. The error group and a link to it. No payloads (events, responses, bodies) are sent to Slack.
What alerts cover. Handler errors, init errors, out-of-memory kills, crashes and timeouts. Throttle alerts are optional.
Weekly email digest
Each week, workspace members get an email with new error groups, the top error groups with their trend, and totals of failures and throttles. Members can opt out of the digest.
Self-hosted
- Slack: create a Slack app from the manifest included in the repository, then set the Slack environment variables on the API.
- Email: set
IVY_SMTP_URLandIVY_EMAIL_FROMso Ivy can send the digest. - Anything else: the
on-error-group-createdhook runs an executable from your hooks directory (IVY_HOOKS_DIR) whenever a new error group appears, for example to open an issue or call your paging tool.
The repository's deploy README lists the exact variables.
Not supported
Metric, latency or cost alerts, custom alert rules beyond the thresholds, and paging integrations such as PagerDuty are not part of Ivy. For those, use CloudWatch alarms, or the on-error-group-created hook on a self-hosted install.