Tracing: the flight recorder your AI needs
What it is — in one coffee-break
Tracing means recording what your AI system actually did: which model was called, with what input, what it answered, which tools it used, how long it took and what it cost. A trace is the flight recorder for an AI workflow. Without it, an AI failure is a mystery you reconstruct from memory; with it, it's a timeline you read in minutes.
AI systems need this more than normal software because they fail politely: an agent produces a well-formed, confident, wrong answer, and nothing crashes. The 2026 observability guides put it plainly — agents fail in ways that look like success. Only the trace shows that the model retrieved the wrong document, or called the same tool five times, or silently fell back to a cheaper model.
When you actually need it (and when you don't)
Experimenting in a chat window? You don't. The moment an AI system runs unattended — a nightly pipeline, a customer-facing assistant, an agent with access to your systems — tracing stops being optional. It's how you answer the three questions every operator eventually asks: why did it do that, what did this month cost, and is quality drifting?
The good news: this has standardized. OpenTelemetry — the same open standard normal software uses for monitoring — now has GenAI conventions covering LLM calls, agent steps and tool executions, with MCP tool-call tracing added in 2026. Open-source tools like Langfuse (28,000+ GitHub stars, self-hostable, acquired by ClickHouse in January 2026) and Phoenix give small teams the whole stack for free. The bad news, per a Gartner figure in the same research: only about 15% of AI deployments instrument observability at all. The other 85% are flying blind.
How to recognize good vs bad implementations
In the audits, Tracing (Tr) is where platform maturity shows. Gemini scores 8.5 and Microsoft 365 Copilot 8 — enterprise stacks with real audit trails. n8n scores 8: every workflow execution is replayable step by step, which is exactly what a small business needs when an automation misbehaves. The other end is instructive: DeepSeek scores 2 (an engine with almost nothing around it) and consumer creative tools like Suno (3.5) offer effectively no visibility. The buyer's question: when this tool does something wrong, what exactly will you be able to show me?
What this costs
Self-hosted Langfuse or Phoenix: €0 in licenses, a small server, and an afternoon of setup — the same shape as the automations in our Blueprints. Managed options run roughly €0–50/month at small-business volume. Compare that with one undiagnosed bad week of a customer-facing assistant, and tracing is the cheapest insurance in the stack.
Where to see it scored
Tr scores with reasons: n8n (8), Gemini (8.5), Claude (8), DeepSeek (2). Tracing is also what makes the next discipline possible: evaluating whether outputs are any good (Ev — covered later in the track).