Lambda error alerts in Slack, and a weekly digest

Slack alerts per error group

• Add to Slack and pick the channel. Each alert describes the error group (the function and its error) with a View in Ivy link.
• First seen, then throttled. The first occurrence of a new error group sends a message right away. After that, the same group posts again at most every 60 minutes or every 100 occurrences, whichever comes first. Both thresholds can be changed per project.
• No payloads in Slack. Messages carry the error, not your request or response bodies. The data stays in Ivy.
• Covers failures outside the handler: init errors, out-of-memory kills, crashes and timeouts alert like any handler error. Throttle alerts are optional.

Weekly email digest

Once a week, each workspace member gets a summary:

• new error groups that week;
• the top error groups, with their trend against the week before;
• totals of failures and throttles.

Members can opt out of the digest.

Self-hosted

On a self-hosted install, Slack and email are turned on with environment variables. A Slack app manifest is included, so creating your own Slack app takes a minute, and email goes through your SMTP server. For anything else, the on-error-group-created hook runs your own script when a new error group appears, for example to open an issue in your tracker. See setting up alerts.

What alerts don't do (yet)

Alerts are deliberately simple. Ivy does not have:

• metric, latency or cost alerts;
• custom alert rules beyond the per-project thresholds above;
• paging integrations such as PagerDuty or Opsgenie.

If you need those today, pair Ivy with CloudWatch alarms, or use the on-error-group-created hook on a self-hosted install.