Leadership & Culture
Protecting time off means changing the SRE workload
Protect time away through explicit coverage, recovery policies, and realistic planning instead of relying on individual boundary-setting alone.
Nate Reuck
SRE and platform engineering practitioner. Writing about what actually works in production.
Leadership & Culture
On-call overload: respond to the workload before it becomes normal
Use interruption patterns and responder feedback to change paging, coverage, and recovery expectations when on-call work becomes unsustainable.
Leadership & Culture
The reliability decisions an SRE leader must make
Give teams clear service ownership, decision authority, and capacity to act on reliability evidence before the next incident.
AIOps
Observability With AIOps: A Practical Evaluation Guide
Use AIOps to connect operational evidence, then test whether it improves investigation without hiding missing signals or unsupported conclusions.
AIOps
AIOps anomaly detection: unusual does not always mean actionable
Choose a baseline, evaluate false positives and missed incidents, and connect anomalies to an operational decision before paging on them.
How-To
Distributed tracing: choose the first request path to instrument
Start tracing with a customer-critical path, then test propagation, sampling, and whether the trace supports a real investigation.
AIOps
Route support tickets with NLP and a reliable fallback
Build a ticket-routing evaluation around real ownership, uncertain cases, and correction cost. Start with an honest baseline before adding a model.
AIOps
Continuous monitoring needs a visible stale-data state
Design continuous monitoring around freshness, coverage, delivery, and response ownership before adding analysis or automation.
SRE
Service level objectives: define the experience you intend to protect
Choose an SLI, target, and evaluation window that reflect user experience, then agree on the decisions an SLO result will change.
How-To
Read a distributed trace without mistaking it for the whole system
Understand spans, parent-child relationships, retries, and missing evidence so traces support a careful diagnosis.
SRE
SRE feedback loops: check whether the signal still means the same thing
Connect telemetry, customer reports, decisions, and verification so improvements in a dashboard reflect improvements in the service.
SRE
Error budgets: calculate the allowance and agree how to use it
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.