How-To
OpenTelemetry for SRE: connect the signals that explain a request
Understand instrumentation, context propagation, and the Collector, and why consistent telemetry still needs careful signal design.
Guides
Walkthroughs for observability, incident response, and AI-assisted operations.
AIOps fundamentals
Start with what AI can do for operations, and where judgment still matters.
Read AIOps fundamentals ↗Observability for SRE
Make metrics, logs, and traces work together.
Read Observability for SRE ↗Incident management with AI
Build an incident response practice that learns.
Read Incident management with AI ↗Practical articles
Instructions, examples, and implementation notes.
How-To
Where SRE and platform engineering need an explicit handoff
A practical ownership model for shared platforms, service reliability, incident command, and the work that falls between teams.
How-To
Postmortem risk treatment: decide what the fix actually proved
Separate delivered postmortem actions from demonstrated risk reduction, close only tested scope, and record residual exposure with a treatment worksheet.
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
NotebookLM for SRE: build a source-backed incident dossier
Use a curated notebook to compare runbooks and incident evidence, while keeping citations, freshness, and operational authority in view.
AIOps
Connect PagerDuty, Jira, and Slack without losing incident state
A design guide for an incident assistant that handles duplicate events, partial failures, and reviewed AI summaries across tools.
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.
How-To
Customer reliability engineering: connect the report to the service
Translate customer symptoms into an owned investigation while preserving impact, uncertainty, and a useful communication loop.
How-To
Alert trust: decide which signals earn an interruption
Decide which alerts earn an interruption using urgency, reachable authority, coverage evidence, and a practical alert acceptance record.