Open the affected request
Start with the checkout operation associated with the customer report and locate its available trace.
Sense / Collect
Follow a request across its service boundaries.
Sense connects request execution across services within Unified Observability. Distributed traces help engineers examine the path an operation takes and identify the span that deserves investigation when a customer-facing request fails to complete as expected.
Distributed tracesSense
Follow checkout request req-checkout-c47 through the order and payment services.
In the workspace
Entry request
POST /checkout · req-checkout-c47
Service path
checkout-api → orders → payments
Span to inspect
Payment authorization · Error recorded
Follow the failed operation into the service where it surfaced.
How it works in Sense
The engineer can see where the request encountered an error and inspect the span context before assigning the investigation. A failed payment span identifies a useful starting point; its underlying cause still requires supporting evidence.
Follow execution across services
Inspect the parent and child spans to understand how the request reached the payment authorization step.
Examine the failing span
Review the recorded error and relevant attributes, then use that context to investigate the payment service or its dependencies.
Bring Sense to your team.
Explore distributed traces around your company’s workflows.