Async context propagation: trace message queues and background jobs

<p>A user triggers an invoice, the API answers in 80 ms, and a worker generates it from a queue forty seconds later. In your tracing tool you see two unrelated stories. Async context propagation did not happen: nobody wrote the trace context into the message, so the worker started a new trace.</p> <p>This tutorial is for SRE and platform teams that run message queues (RabbitMQ, SQS, Redis, a jobs

Read the source →