Why Your AI Agent Health Check Is Lying to You

Your monitoring dashboard shows green across the board. Process running. Port responding. CPU normal. Memory stable. But your AI agent hasn't done anything useful in four hours. The problem with traditional health checks Traditional health checks answer one question: "Is the process alive?" For web servers, that's usually enough. If Nginx is running and responding on port 80, it's probably serving pages. AI agents are different. An agent can be alive without being productive. The process is running, but the main work loop is stuck on a hung HTTP call, waiting on a deadlocked mutex, or spinning in a retry loop that will never succeed. Three ways health checks lie 1. PID exists ≠ working systemctl status my-agent says "active (running)". But the agent's main loop has been blocked on requests.get() for three hours because an upstream API rotated its TLS certificate and the connection is hanging without a timeout. The health check thread runs independently and reports "I'm fine" every 30 s