Search across all documentation pages
6 pages in this section.
Learn the mental model behind tracing agent spans, logging prompts, and alerting on cost anomalies in Claude-powered applications.
Emit OpenTelemetry spans for every model call and tool invocation in a Claude agent loop, so you can see latency and failure points across a multi-step run.
Build a structured log schema that captures the prompt, response, token counts, model, latency, and request ID for every Claude API call.
A checklist for tying a spike in Claude call latency, error rate, or refusals back to your last deploy instead of treating it as a mystery.
A checklist of best practices for instrumenting Claude applications so cost and reliability issues surface early instead of at the end of a billing cycle.