Search articles

Search titles and article text.

Test evidence retrieval, long-session consistency, tool boundaries, and cost before letting a model influence production changes.

February 6, 20264 min read

Account for context limits, retries, latency, and the work behind a useful result.

March 14, 20264 min read

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

February 13, 20264 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

Read validated architectures as a starting point for workload, recovery, and support testing, not a promise of automatic reliability.

April 2, 20254 min read

Counters, gauges, and distributions answer different questions. Build metrics that preserve scope, denominators, and the evidence behind an incident.

September 30, 20233 min read

Define coverage, escalation, training, and recovery time before assigning the calendar. Review workload as well as shift counts.

September 29, 20233 min read

Give teams clear service ownership, decision authority, and capacity to act on reliability evidence before the next incident.

September 28, 20233 min read

Understand spans, parent-child relationships, retries, and missing evidence so traces support a careful diagnosis.

September 28, 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

The stable Kubernetes attributes processor helps connect AI-agent traces to their workloads. Check the metadata joins before upgrading.

September 21, 20264 min read

Define the action, contain its scope, and verify what changed at the destination.

March 26, 20265 min read