Organizing ownership: How we assign errors in our monolith
At incident.io, we streamline our monolith by assigning clear ownership to chunks of code and enforcing it with CI checks. Tagged errors are automatically routed to the right team, reducing on-call stress and keeping our system efficient as we scale. Here's how we do it.
Martha Lambert
Building On-call: Our observability strategy
Our customers count on us to sound the alarm when their systems go sideways—so keeping our on-call service up and running isn’t just important; it’s non-negotiable. To nail the reliability our customers need, we lean on some serious observability (or as the cool kids say, o11y) to keep things running smoothly.
Martha Lambert
Why you need an incident timeline
Learn how to get the most from your incident timeline.
Martha Lambert
Driving a customer-focused incident response process
Minimising customer impact doesn't always align with shortest time to a fix. Here's how to make your incident response process revolve around your customers.
Martha Lambert
Tell the story of your incident with timeline curation
Why telling the story of your incident is vital to finding the most useful insights.
Martha Lambert
Introducing Incident Types
Use incident types to optimise your incident response for the situation at hand, and gain insights into incidents sliced across your organization.
Martha Lambert