County operators receive user latency tickets while ingress-controller pods show sustained CPU saturation. What troubleshooting principle does correlating those signals illustrate?
Select an answer to reveal the explanation.
Short Explanation
Tickets say 'slow'; metrics say the ingress pods are pegged—connect those dots. Symptom plus saturation beats guessing in the dark.
Full Explanation
Effective troubleshooting correlates external symptoms such as latency with resource saturation on components in the path, for example ingress controllers. Presence of Services or Ingress objects alone does not prove health, and PVC bind state does not explain request latency. Measured CPU saturation provides a concrete causal lead.