Martha Lambert's posts
Building Investigations: what it takes to build an AI SRE
We spent the last two years building Investigations, our AI SRE. In this post, go behind the scenes of the work done and why build vs. buy is one of the most important decisions engineering teams are making right now.
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.
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.
Why I joined an engineering team of 6
6 months in, Martha reflects on why she chose to join the engineering team of an early stage start-up, and what she’s learnt since.
Why you need an incident timeline
Learn how to get the most from your incident timeline.
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.
So good, you’ll break things on purpose
Ready for modern incident management? Book a call with one of our experts today.
We’d love to talk to you about
- All-in-one incident management
- Our unmatched speed of deployment
- Why we’re loved by users and easily adopted
- How we work for the whole organization
