Users report that a service "feels slow" but no errors are being raised. Which signal should be examined first?
Select an answer to reveal the explanation.
Short Explanation
Slow but succeeding is the definition of a latency problem. Check saturation next for the cause, but latency is where the symptom lives.
Full Explanation
The correct choice is latency, since latency measures how long requests take. When a service returns correct responses slowly, it shows elevated latency with a flat error rate, matching the report exactly. It is worth checking saturation next for the cause, but latency is where the symptom lives. The errors signal is incorrect because requests that succeed are not errors; slowness only becomes an error once something times out, which has not been reported. The deployment date signal is incorrect because deployment schedule is not a measurement of current behaviour, though a recent release is worth correlating once the symptom is confirmed. The server hostnames signal is incorrect because host inventory does not describe performance. Exam caveat: map the reported symptom to the signal that measures it: slow means latency, failing means errors, overloaded means saturation.