GuideAI in production
Recovering an automation write after a timeout
A missing response can leave a worker already created. Durable operation IDs and the destination’s idempotency contract let a replacement executor recover the original request.
How-To
Practical methods you can take back to your team.
GuideObservability
Why a Prometheus error-rate query can return no data
Zero errors, no traffic and absent series produce different PromQL results. Synthetic tests show how ratios, fallback zeros and absence checks behave for a checkout service.
GuidePlatform engineering
Disruption budgets and the capacity left behind
Plan an inference-service node drain with a scoped disruption budget, replacement-capacity checks and a practical maintenance worksheet.
GuideAI in production
Prompt caching: measure the cost of useful work
What prompt-cache hits save once retries and failed work are included in task cost, with a local calculator and ledger.
GuideAI in production
How to evaluate incident-response agents
Build repeatable cases and check recovery independently, with a runnable Python grader.
ExplainerObservability
Connect the signals with OpenTelemetry
Use instrumentation and context propagation to connect the evidence in an investigation.
ExplainerPlatform engineering
The SRE and platform handoff
Clarify ownership across shared platforms, service reliability, and incident response.
GuideIncident response
What did the postmortem fix prove?
Separate a completed task from evidence that the underlying risk was reduced.
GuideIncident response
Why a 5 Whys investigation can branch
Evidence can split a 5 Whys investigation into several contributing causes. A concurrency example shows how to turn those explanations into useful tests.
GuideAI in production
Comparing incident sources with NotebookLM
Conflicting restart instructions show where a source-backed notebook helps: finding the relevant passages, dates and exceptions for the runbook owner.
GuideIncident response
Keeping incident state consistent across PagerDuty, Jira and Slack
A reference design for duplicate deliveries and partial API success, with durable incident identifiers and summaries drawn from the resulting record.
GuideObservability
Grafana dashboards for incident response
Regional failures can disappear in fleet averages. Grafana queries, population labels and linked traces help responders find the affected requests.