Reducing our pager load

Incident.io, a small team that provides a great product to its customers, has been using an app that raises errors via Sentry and alerts them through pager. However, they found this system too noisy as it lacks the concept of working hours and is sensitive to all exceptions. To reduce their pager load without compromising on error detection, they implemented several strategies: 1) introducing expected errors with helpers that return a warning or an error; 2) labeling best effort paths by setting default urgency in context; 3) only paging for transient errors after three failed attempts; and 4) not paging for issues related to demo accounts. These changes significantly reduced their pager load, improving the team's work-life balance without compromising on error detection and fixing.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.