This website uses cookies to ensure you get the best experience.
Learn more.
A trace shows most request latency inside one downstream service call, while local handler computation is brief. Which investigation follows the evidence?
Published
- Inspect the slow downstream call, its retries, resource limits, and request parameters before optimizing unrelated local code.
- Disable tracing permanently because it revealed a slow dependency.
- Rewrite only the local response JSON serializer despite its negligible measured duration.
- Assume every latency issue is a cold start regardless of the trace.
Comments — 0
Sign in to comment