A Kubernetes deployment succeeds, but the application starts returning errors. CPU utilization looks normal, yet response times climb. An autoscaler adds capacity without improving performance, and the on-call engineer spends the next hour moving between dashboards, deployment histories, logs, and configuration files. The difficulty is rarely a lack of monitoring data. It is determining which signals matter, how they relate, and what action will restore service without introducing another failure.