GuideSLOs & reliability
Trace the journey from request to result
Follow an export from acceptance to authorized retrieval, mapping handoffs, dependencies, owners and the checks that distinguish failures.
AI in production. Reliability in practice.
Latest edition ·The latest analysis
Read commands and find help
Read Bash commands, find the right help and see how quoting, expansion and redirection change what actually runs.
Read the storyFrom the publication
The latest
GuideIncident response
Set severity, roles and decision authority
Organize a Dispatch incident with impact-based severity, accepted roles and a concrete route to deciding whether a rollback can proceed.
GuideObservability
Map what the telemetry needs to explain
Use a worked export timeline to separate queue wait from processing, connect job records and choose the next observation.
GuideAI in production
OpenCode 2.0 explained: what it does and how to use it
OpenCode is an open-source AI coding assistant that works with your project’s files and tools. Here’s what that means, what changed in 2.x, and how to try a small repair without handing it your whole environment.
Field guides
Get closer
to the evidence.
Follow a request. Review the code. Find out what actually happened.
Explore the guidesKeep the traces that explain a failure
GuideObservability
OpenTelemetry tail sampling through a checkout failure
Tail sampling selects recorded traces by error, latency and other evidence. A checkout timeout shows how routing, waiting time and memory affect the trace a responder can retrieve.
Give AI code review a useful job
GuideAI in production
CodeRabbit: how to use AI code review
CodeRabbit brings AI feedback into pull requests, editors and the CLI. A retry loop that exceeds its caller’s deadline shows the kind of finding that can repay review time.
Recover when a tool call times out
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.
Put it into practice
From a signal to a plan.
Trace the minutes, check the budget and write the recovery steps. Free tools. No account needed.
01 / Incident timelineIllustrative example
Every minute
tells part of the story.
Reconstruct the response, from the first failure to verified recovery.
16minOnset to recovery
10:02Onset10:03Detected10:06Investigation10:18Recovery
02 / Error budgetIllustrative example
Know your
room for failure.
75%remaining
Request SLO99.9%
Eligible requests1,000,000
Allowed bad requests1,000
Bad requests used250
Bad requests left750
03 / Runbook builder
Give the next responder a head start.
Turn what you know into a procedure someone can follow.
01 Scope02 Action03 Recovery check
Start a runbook Companies & products