
AI logging: what to capture around a model request
Trace a model request through timings, retries, tool calls, configuration changes, and outcomes without collecting every message.
Read AI logging: what to capture around a model requestLog Mic Lab / Category
This collection focuses on the application boundaries around model requests: correlation, attempt handling, observed duration, outcomes, and deliberately scoped content capture. Begin with the AI logging article, then use the linked token guide for usage reconciliation. The emphasis is on an inspectable application workflow with clear field meanings and limits, rather than a promise that more telemetry explains every model output.
AI logging gives model-driven workflows an inspectable history. Follow application operations, distinguish attempts from completed work, and keep sensitive content out of routine telemetry unless there is a defined reason to capture it. Visit the AI Logging topic guide for the starting questions, a short checklist, and the scope of this collection.
1 guide · Latest publication first

Trace a model request through timings, retries, tool calls, configuration changes, and outcomes without collecting every message.
Read AI logging: what to capture around a model requestExplore a shared question across different kinds of logs. Each collection brings together relevant guides and a useful reading path.