Protocol
Trace one transaction across a component boundary
A correct value in the sender’s log does not show what the receiver received. Compare the same transaction on both sides of one boundary.
Before you use it
- Use when
- Several services, interfaces or processing steps could plausibly own the same symptom.
Keep this limit in mind
- A boundary check can be misleading when retries, caches, asynchronous queues or hidden transformations change the path.
Current editorial reading
Capture a useful comparison
Name the two components, the input, the expected transformation and the observed output. Prefer an existing trace; if a new probe is needed, use authorized, safe test data. For example, compare a queued job’s sent payload with the payload consumed downstream, keeping the transaction identifier and relevant timestamps together.
Let the result narrow the next question
If the input is already wrong, investigate upstream. If a correct input becomes wrong, inspect the transformation. First check that caches, retries or asynchronous processing have not made you compare different attempts. Record an inconclusive result when they have. A single successful probe cannot clear a component of an intermittent fault.
Take it with you
Leave a small record of the boundary, input, expected and observed result, and next test. Useful progress can be a narrower question; it need not eliminate a suspect.
Sources and evidence (1)
What we checked
Google SRE recommends examining component interfaces and testing expected transformations.
Selected official passages inspected on 2026-10-04. The transaction record is an editorial adaptation.
Effective Troubleshooting · Simplify and reduce
Operational tests can change state, be confounded, or provide only suggestive evidence.
This limits the original card’s requirement that every probe eliminate a component. No system was probed during this review.
Effective Troubleshooting · Test and Treat; test-design considerations
Editorial sources (1)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingTrace one transaction across a component boundary
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
Google SRE recommends examining well-defined component interfaces and injecting known test data to check expected transformations.
Interface probes can disturb stateful systems; use safe inputs and preserve context needed to interpret the result.
Effective Troubleshooting · Simplify and reduce
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details