Trace context propagation passes trace identity and parent span information along with cross-service requests. This lets spans recorded by separate services join into one trace.
In the demo, the same ID travels through a gateway, API, and database. If a proxy or asynchronous step drops that context, the trace breaks into disconnected pieces.
When to use
Use it when instrumenting calls across services so they form one distributed trace.