An agent can tell you what it did, and be wrong about it. This site starts from one line printed to a terminal and climbs, one idea at a time, to structured logs, metrics, traces, audit events, redaction, service level objectives, replay and cost, asking one question at each step: what does this record let me prove about what happened?
A roof-assessment call times out, the agent retries, the run is checkpointed, and an underwriter decides hours later. Weeks after, someone asks why the quote was declined. The answer is spread across gateway logs, model spans, a provider timeout, a retry, a checkpoint and an audit event, and only the right identifiers join them into one story you can trust.
From stdout and structured logs to spans and span trees; what each signal answers, and the identifiers that join them across HTTP, queues, tools and models.
Token usage, model calls, retrieval and tool steps; the GenAI semantic conventions as read today, with their development status stated.
Audit logs against diagnostic logs, redaction, access, retention and sampling, and the trade-offs of the common log and trace backends.
Objectives and alerts worth waking for, replay and its limits, incident response, golden-case promotion, and cost per run.