ExplainerAI in production
What Kimi K3’s million-token context offers SRE teams
Kimi K3 can keep a larger incident record in view. Its practical value depends on evidence handling, agent integration and the cost of useful investigation.
AI in production. Reliability in practice.
Latest edition ·The latest analysis
Instinct: from a text or call to a confirmed task
Instinct brings personal tasks into connected services. A hypothetical booking and notification worker show how permission, provider confirmation and uncertain results affect what happens next.
Read the storyFrom the publication
The latest
GuideObservability
Tracing an AI request through Cloudflare and its origin
Follow a slow AI request from Cloudflare to an instrumented origin, configure sampling, and verify that the trace preserves the evidence needed to investigate.
GuideObservability
Measuring a latency SLO with Prometheus histograms
Build a latency SLI from Prometheus histogram buckets, include failed requests, and compare classic and native queries with a worked search-service example.
GuideIncident response
An SRE incident handoff in ChatGPT Space
A synthetic order-service incident follows a shared handoff through page edits, new findings and shift change, including the review and access work involved.
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
Less blank page.
More working plan.
Free reliability tools. No account needed.
Open the workbenchThe AI tools guide
Find the right AI tool for the job.
Coding assistants, code review and agent supervision.
Browse the guideCompanies & products