Notes from reading agent conversations.

People type analytics when they want to know if the agent is working. One job is the run. The other is the person.

Traces record software execution. Analytics measures human task completion. TWO DIFFERENT PARADIGMS ENGINEERING TRACE invoke_agent (1.2s) tool_search (420ms) llm_generate (680ms) ✓ 200 OK · 0 Exceptions PRODUCT ANALYTICS find the source (96.2%) read it (528 stopped) write summary (64% done) ✗ User abandoned at Turn 9 THE CORE GAP Traces tell you whether the software ran. Analytics tells you whether the person succeeded.

What is AI agent analytics?

A practical guide to reading live conversations: uncovering what people came to do, where the agent lost them, and why traces and latency aren't enough.

11 min read1 Sep 2026

Read the post
A production conversation passing through execution telemetry, evaluation, and user outcome evidence. ONE PRODUCTION CONVERSATION PROMPT TOOL CALLS RESPONSE PERSON TRACE what ran? latency · errors · cost EVALUATION was it acceptable? quality · safety · drift EXPERIENCE did they finish? task · intent · replay Production observability needs all three readings.

What is AI agent observability?

A practical guide to the traces, evaluations, metrics, silent failures, user outcomes and investigation workflow behind an observable production agent.

15 min read27 Aug 2026