Sustainable on-call: make workload relief change the plan
Connect on-call interruptions, specialist demand, and recovery work to a concrete capacity decision using an on-call workload worksheet.
Search titles and article text.
Connect on-call interruptions, specialist demand, and recovery work to a concrete capacity decision using an on-call workload worksheet.
Turn reliability policy into a release decision with fresh evidence, limited exceptions, and a clear path to resuming normal changes.
Connect an SLO’s allowance to planning and release behavior, with explicit ownership, exceptions, and treatment of measurement gaps.
Adapt a complete SLO record, worked budget examples, and an exception log without confusing bad requests with minutes of downtime.
Measure a representative workload, identify the limiting resource, and test one reversible change instead of applying a universal sysctl recipe.
Locate the delay, choose a bounded intervention, and measure recovery quality alongside elapsed time.
Use models for test suggestions and change analysis while keeping artifact identity, promotion rules, and rollback checks enforceable.
Choose representative traffic, define promotion criteria, and verify rollback compatibility before expanding a release.
Use consistent onset and discovery timestamps, include customer-reported incidents, and interpret the average with its sample and uncertainty.
Containers package processes; orchestration reconciles desired state. Reliability still depends on probes, capacity, dependencies, and application behavior.
Translate incident findings into funded changes with an owner, a test, and evidence that the relevant failure mode became less likely or less costly.
An error budget translates an SLO into an allowed amount of bad service. Its value comes from the decisions attached to consumption and burn rate.