Search articles

Search titles and article text.

Separate a completed task from evidence that the underlying risk was reduced.

March 24, 20265 min read

Prepare evidence, reconstruct the timeline, examine contributing conditions, and choose follow-up proportionate to the incident.

September 30, 20233 min read

Follow evidence through technical failure and incident response, then test whether the proposed correction changes the mechanism.

February 13, 20264 min read

Translate incident findings into funded changes with an owner, a test, and evidence that the relevant failure mode became less likely or less costly.

September 29, 20233 min read

Use models for test suggestions and change analysis while keeping artifact identity, promotion rules, and rollback checks enforceable.

March 19, 20253 min read

Examine what people knew and could do, then assign improvements that address the conditions behind the incident.

September 30, 20233 min read

Connect telemetry, customer reports, decisions, and verification so improvements in a dashboard reflect improvements in the service.

September 28, 20233 min read

Use a curated notebook to compare runbooks and incident evidence, while keeping citations, freshness, and operational authority in view.

February 12, 20264 min read

Locate the delay, choose a bounded intervention, and measure recovery quality alongside elapsed time.

March 23, 20254 min read

Define who does the work, who decides, and who accepts risk so ownership remains useful during incidents and follow-up.

October 7, 20233 min read

Use the free SRE books as references for a concrete service problem, then adapt and test the practices against your own constraints.

September 18, 20233 min read

Check agent status, terminal persistence, and recovery before adopting Herdr.

September 21, 20268 min read