When well-behaved agents trigger disaster
It’s 2:17 a.m., and your application monitor flags elevated database latency. Before your on-call engineer finishes reading the alert, three agents have already responded. The performance agent doubles the database capacity. The cost agent, seeing what appears to be overprovisioning, starts consolidating …