The Observability Layer Your AI Agent Is Missing
Logs tell you what happened. Traces tell you why. The three layers of agent observability, and where silent failures actually live.
I walk through a real production failure from my own system. My business ops agent confidently reported a completed task it had silently failed. Logs were clean. The dashboard was green. A single trace showed exactly why. This is Part 2 of the Agent Quality series, based on Google’s Agent Quality white paper.
Building an AI agent?
I help teams design and ship agentic systems — from architecture to production.
See how I can help
I Added ACP to My Mastra Agent So It Can Work in Repos
ACP is the layer that lets my Mastra agent hand real repo work to Claude Code instead of stopping at advice.
Stop Giving Your Agent Every Tool
Large tool catalogs break agent context. Tool search fixes that by letting agents discover and load only what they need.
Stop Letting AI Agents Run the Whole Workflow
One inbox agent should not classify, research, score, route, and draft replies in one loose loop.
Harness Engineering: 4 Levers to Diagnose Any AI Agent
Most agent failures aren't model failures. They're harness failures. Here's the 4-lever framework I use to diagnose what broke.
Get new videos and posts by email
Weekly videos on AI engineering, plus deeper dives in the newsletter.
Occasional emails, no fluff.