AI Observability: What to Monitor in Production LLM and Agent Systems
Production AI needs observability across prompts, retrieval, tools, latency, cost and quality. Here is what engineering teams should monitor and why.
By Maya Chen, Women in AI Editorial Fellow ยท 24 August 2026
A production AI application can be online, fast and completely wrong.
That is why traditional observability is not enough for LLM and agent systems. Engineering teams still need infrastructure metrics, but they also need visibility into the behaviour of the model and the components around it.
Trace model calls
Teams should be able to see which model was called, with which configuration, and how long the request took.
This helps diagnose changes caused by model versions, prompt updates or routing logic.
Monitor latency and cost
AI applications often make several model calls per user request.
Agents may make many more as they plan, retrieve and use tools. A workflow that looks inexpensive in testing can become costly at production scale.
Track token usage, model cost and latency by feature or workflow rather than only at account level.
Observe retrieval
For RAG applications, log which documents or chunks were retrieved.
When an answer is wrong, engineers need to know whether the model ignored good evidence or never received the right evidence in the first place.
Retrieval observability shortens that diagnosis.
Trace agent tools
Agent traces should capture tool selection, inputs, outputs and sequencing.
AWS evaluation guidance increasingly emphasises execution traces because agents can reach a plausible answer through an unreliable path.
Without traces, debugging becomes guesswork.
Monitor quality samples
Not every production interaction can receive human review, but teams can sample traffic for automated and manual evaluation.
Useful dimensions may include task success, factuality, groundedness, harmfulness and process compliance.
Trend these over time so quality regressions become visible after model, prompt or data changes.
Track failures users experience
Explicit user feedback is useful but incomplete.
Also monitor retries, abandoned sessions, repeated rephrasing, escalation to humans and tool errors. These behavioural signals can reveal frustration users never report directly.
Connect technical and quality incidents
An outage is not the only production incident worth investigating.
A retrieval index that silently becomes stale, an agent that starts overusing a tool or a model update that changes refusal behaviour can all create material quality problems.
AI observability should feed into the same incident-management discipline as other production systems.
The goal is explainable operations
You may not be able to explain every internal model decision, but you should be able to reconstruct what your application did.
Which model ran? What context did it receive? Which documents were retrieved? Which tools were called? What did they return? How did the final output score against your quality checks?
That operational visibility is what lets teams improve AI systems systematically instead of debugging by anecdote.