Skip to content

Worked journey

Find out where cancellation is failing

After a rollout, support reports that cancellation stopped working on an older client. In this illustrative case, the team starts with a request trace and asks which version and endpoint it actually observed.

OpenTelemetry tracing investigation example

The trace

Investigate a cancellation failure using an OpenTelemetry trace, versioned source, coverage gaps and a proposed regression check.

The trace stops after the service. Two explanations fit, and each has its own check.

trace 4f2a…c81 · build orders-api 2.14.0 · mobile-app 3.2 · illustrative

POST /orders/{id}/cancel
OrderController.cancel
OrderService.cancel
OrderRepository.updateStatus
no span

The trace reaches the service and stops. That could mean the write never ran, or that nobody instrumented it. The twin shows both hypotheses and the check that would settle each one, instead of naming a cause.

Walkthrough

Step by step.

  1. Compare runtime and source evidence

    An observed validation failure on an older request supports a compatibility hypothesis. A trace only as far as the order service leaves the write unobserved. Confirm deployment identity before matching a span to a versioned source line.

  2. Follow the evidence to the right fix

    Reproduce the older request to verify a behavioural regression. If the gap is missing instrumentation or dropped export, inspect that path and reproduce the coverage failure separately. Trace scope and sampling determine what the investigator can claim.

  3. Turn the result into reviewed work

    Link the incident evidence to a draft compatibility or instrumentation story. Write the expected outcome, a regression boundary and a check against the deployed version. The story proposal remains a plan until a reviewer agrees on scope.

Two hypotheses, two checks

ObservationWhat to investigateWhat would settle it
Validation refusal on an older requestPossible contract regressionReproduce the old request against the implicated build
No span after the order serviceUnknown write execution or missing observationCorrelate application and collector evidence
A write error span existsAn instrumented write encountered an errorInspect the deployed write path before naming the cause