This document describes how a SDK should propagate information between different services to connect all telemetry (errors, profiles, replays, transaction) from those services into one trace.
For an overview see Distributed Tracing in the product docs.
With these containers you can propagate a trace to a down-stream service. By either
baggageHTTP headers (when doing outgoing HTTP requests),
baggageas meta data (when putting tasks into a queue, details are specific to the queue you want to support), or
- setting environment variables (when calling another process). In this case the env variables should be called
The SDK running in the receiving service needs to make sure to pick up incoming trace information by
baggageheaders for each incoming HTTP request,
baggagemeta data when retrieving an item from a queue, or
- reading the environment variables
SENTRY_BAGGAGEon start up.
This trace information should be stored in the "propagation context" of the current scope. This makes sure that all telemetry that is emmited from the receiving service to Sentry will include the correct trace information.