Context propagation
Context propagation is the transmission of execution or request context across component, thread, process, asynchronous, or network boundaries so it remains available to related operations.
Cloud Observability in Action
Context propagation is the transmission of request-identifying context across processes and network boundaries.
- How it is used
- Connects service-level work into end-to-end distributed traces for monitoring, latency optimization, troubleshooting, and correlated log analysis.
- How deep it goes
- Explains identifiers, parent-child forwarding, headers, stitching, failures, and costs, but stops short of implementation code.
- Examples
- Uses an e-commerce billing-to-payment-provider call and contrasts W3C headers with proprietary headers.
- What you can do after
- Diagnose broken traces, select header translation remedies, and evaluate propagation costs within an OpenTelemetry-based tracing design.
Read how Cloud Observability in Action explains context propagation →
Spring Microservices in Action
Thread context propagation is the transfer of contextual data from one thread to another so the receiving thread can use that data.
- How it is used
- Preserves request-specific user context when Hystrix moves protected work from a REST-call thread to a command thread.
- How deep it goes
- Implements a custom Hystrix strategy and Callable wrapper that sets UserContext in a ThreadLocal before delegated execution.
- Examples
- Demonstrates copying UserContext from a parent REST-service thread into a Hystrix command and logs correlation IDs.
- What you can do after
- Apply it via a custom Hystrix concurrency strategy and a Callable wrapper that transfers UserContext to command threads.
Read how Spring Microservices in Action explains context propagation →
Also covered in
- 100 Go Mistakes and How to Avoid Them
- gRPC Microservices in Go
- Designing AI SystemsIn early access (MEAP)
What to know first
- trajectoryA trajectory is an ordered record of states, actions, events, or operations showing how an agent or system progresses through an execution or process.
- monitoringMonitoring is the ongoing observation and measurement of a system or process to assess its behavior or condition and detect changes, failures, or other problems.
- microservice architectureMicroservice architecture is a software architectural style that structures an application as independently deployable services, typically organized around focused capabilities and communicating through defined interfaces.
Related concepts
- trajectoryused by · A trajectory is an ordered record of states, actions, events, or operations showing how an agent or system progresses through an execution or process.
- contextuses · In Go, context.Context is an interface carrying cancellation signals, deadlines, and request-scoped values across function and service boundaries.
- trace contextuses · Trace context is request-propagation metadata that associates operations across services with a distributed trace.
Questions about context propagation
What is context propagation?
Context propagation is the transmission of execution or request context across component, thread, process, asynchronous, or network boundaries so it remains available to related operations.
Which Manning books explain context propagation?
Cloud Observability in Action and Spring Microservices in Action.
What should I know before learning context propagation?
Manning books that teach context propagation usually introduce trajectory, monitoring and microservice architecture first.
What kinds of context propagation are there?
Kinds of context propagation include security context propagation.
What is context propagation a kind of?
Context propagation is a kind of propagation. Propagation is the transmission or spreading of information, state, results, or changes to dependent components or elements.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

