An application spans APIs, Lambda, and downstream services. Aggregate error metrics are normal, but some requests are slow. Which evidence is most useful for identifying the latency path?

Published
  1. Distributed traces with propagated correlation and instrumented downstream timings.
  2. Remove all traces because average metrics appear healthy.
  3. Only a count of deployment ZIP files.
  4. Only the maximum password length in the account policy.

Comments — 0