Chapter 5. Agent-Driven Incident Response Pipeline
The same incident, run by five different organizations, will produce five different outcomes. Same alert, same underlying cause, same blast radius. One organization pages a senior on-call who assembles context from six tools in 12 minutes and ships a rollback. Another organization has an agent that throttles noncritical paths in 23 seconds and pages nobody. The technology is not what separates the two. The architecture is. Later in this chapter (see “One Incident, Five Maturity Levels”), I develop this picture in full, the same incident played through all five maturity levels in deliberate detail. The rest of the s the apparatus that makes the comparison meaningful.
Incident response is the first workflow this book applies the four-plane architecture to, and the choice is deliberate. Incidents are high-frequency, high-cost, time-critical, and well understood. Every reader has been on call. Every reader has assembled context under time pressure. Every reader has shipped a fix while uncertain whether it ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access