How-To
What did the postmortem fix prove?
Separate a completed task from evidence that the underlying risk was reduced.
Search articles
Search titles and article text.
AIOps
The operational cost of AI tokens
Account for context limits, retries, latency, and the work behind a useful result.
How-To
Use the 5 Whys without forcing an incident into one cause
Follow evidence through technical failure and incident response, then test whether the proposed correction changes the mechanism.
AIOps
Evaluate Claude Opus 4.6 for operational work
Test evidence retrieval, long-session consistency, tool boundaries, and cost before letting a model influence production changes.
AIOps
From AIOps signals to agent actions: design the handoff
Decide which workflow deserves an agent, where a fixed automation is sufficient, and how to measure the work left for responders.
AIOps
NetApp and NVIDIA: evaluate the storage path behind AI workloads
Read validated architectures as a starting point for workload, recovery, and support testing, not a promise of automatic reliability.
AIOps
Prompt engineering for operators: make evidence and limits explicit
A reusable prompt pattern for incident analysis, with checks for missing facts, unsafe recommendations, and unsupported certainty.
SRE
Error-budget template: calculations and release-policy fields
Adapt a complete SLO record, worked budget examples, and an exception log without confusing bad requests with minutes of downtime.
How-To
Linux filesystem hierarchy: find the state that is failing
Use directory purpose, mount boundaries, and read-only checks to investigate missing files, full disks, and unexpected runtime state.
How-To
Linux performance tuning starts with a bottleneck
Measure a representative workload, identify the limiting resource, and test one reversible change instead of applying a universal sysctl recipe.
AIOps
Evaluate AIOps tools with the work your responders actually do
Compare detection, correlation, investigation, and automation using your incidents, review costs, and failure paths.
Leadership & Culture
SRE accountability needs authority, capacity, and a clear owner
Define who does the work, who decides, and who accepts risk so ownership remains useful during incidents and follow-up.