FAULTDEBUG / OBSERVED CROSS-SERVICE FLOW
Shopping service fault report
Successful responseFailure response / propagationUnknown statusRed node = cause event; dashed node = native crash
Where and why did it fail?
Selected RPC evidence
Select a recorded call or a service node.
Recorded calls
Sorted by local start time. Propagated parent RPC IDs show call ancestry; a shared trace ID alone does not establish causality.
| Service edge | Request path | HTTP | Time (ms) | RPC → parent |
|---|
Evidence scope and unresolved items
- Failure reasons are application-recorded explanations, corroborated with native RPC and crash evidence. Injection settings alone do not establish the cause.
- Python stacks are not captured. Native functions and crash addresses belong to the instrumented C++ boundary module and are resolved against source and Build IDs.
- A receiver may respond after a caller times out. Caller and receiver outcomes remain separate.
- SHA-256 identifies evidence files; it does not authenticate logs or guarantee complete capture.