A slow checkout can leave clues in several services. OpenTelemetry helps connect those clues to the same request, while traces, logs and metrics answer different parts of the investigation.
The edge was quick, but the runbook answer was late. Connect platform and application spans to see whether retrieval, the model call or an unmeasured step held it up.
Start with work you recognize: one synthetic export. Three terminals show its acceptance, background completion and recorded steps without touching a production service.
Send a local service’s telemetry to the wrong port, then compare its recorded job state with missing spans. Repairing telemetry delivery does not bring every old trace back.
The smaller artifact saves 1.44 GiB but generates more slowly in the project’s measurements. Its value depends on whether that space makes a required request possible.
Two lookups overlap, so adding their durations counts some waiting twice. Read the shared timeline to find both the overlap and the time still unexplained.