April 2022 Summaries

Dani has joined incident.io as the Head of Talent, aiming to enhance the company's talent strategy. Previously, they worked at nate and Checkout.com, where they experienced significant growth in employee numbers. Dani is excited about joining incident.io during its early growth stage and plans to fill urgent positions in Sales, Engineering, and the People team. In their free time, Dani enjoys exploring London's coffee shops and would appreciate recommendations for new places to try.

Incident.io is a centralized platform for managing incidents when things go wrong in business operations. To enhance its functionality, the company has launched an API that allows users to connect incident.io with any tool in their stack or even their own applications. The first version of the API focuses on three major use cases: automatically creating incidents from other systems like monitoring tools and ticketing systems; exporting incidents and their to-dos into data warehouses or BI tools for analysis; and configuring roles, severities, and custom fields from external data sources. The API is designed to be flexible and adaptable, allowing users to create custom workflows and automate processes without having to wait for native integrations with specific tools.

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.

Rhys has recently joined incident.io as a member of their sales team, coming from GoCardless where he worked for three years on complex payment problems. He's excited to be part of the growing team at incident.io and is already busy with numerous calls, demos, and interviews. Prior to this role, Rhys worked at a smaller startup that grew from 120 to 300 employees. In his free time, he enjoys golfing and exploring European microbreweries.

The text discusses how to make Go errors work well with Sentry, an error tracking tool. It explains that standard Go errors don't have stacktraces, which makes it hard for tools like Sentry to provide much value. To address this issue, the author suggests using pkg/errors, a library that implements StackTracer errors and is compatible with Sentry. The text also covers how to wrap errors to ensure they include stacktraces and how to de-duplicate stacktraces when wrapping multiple times. Finally, it mentions creating their own version of pkg/errors to better control error production and improve compatibility with tools like Sentry.

Alex is a new engineer at incident.io, previously working with Sophie, Chris, Stephen & Pete at Monzo and open banking at Stripe. They are excited to work on an exciting product that solves real pain points for people. In their personal life, Alex has the fluffiest dog, works on various side projects, takes a ceramics class, and recently bought a CNC milling machine.

Martha, an experienced engineer from Beamery, has joined incident.io as their newest team member. She specializes in finding and implementing simple solutions for complex problems. In her free time, she enjoys exploring new crafts such as sock knitting and pottery. Currently, she is considering getting a rug tufting gun.