QuestionQ110

VerifiedApplying site reliability engineering practices

You are responsible for supporting a large service that has a clearly defined Service Level Objective (SLO). The development team ships new releases of this service several times per week.

If a major incident occurs that causes the service to fall short of its SLO, you want the development team to redirect its efforts away from new feature work and toward improving the service's reliability.

What should you do in advance, before any major incident happens?

Explanation

An error budget policy, developed collaboratively with all stakeholders (development, product management, and SRE/operations), defines in advance what happens when the error budget is exhausted — including that engineering effort shifts from feature development to reliability work. Establishing this policy ahead of time ensures there is organizational agreement and a clear, pre-negotiated process to follow when an incident causes an SLO miss, rather than having to negotiate priorities reactively during or after a crisis. This is the standard Google SRE practice for aligning reliability and feature-velocity trade-offs.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!