diff --git a/docs/platforms/python/configuration/options.mdx b/docs/platforms/python/configuration/options.mdx index 177fe3aa2e0d03..9ed296b70b552c 100644 --- a/docs/platforms/python/configuration/options.mdx +++ b/docs/platforms/python/configuration/options.mdx @@ -378,6 +378,30 @@ If `trace_propagation_targets` is not provided, trace data is attached to every + + +If set to `True`, the SDK will only continue a trace if the `org_id` of the incoming trace found in the +`baggage` header matches the `org_id` of the current Sentry client and only if BOTH are present. + +If set to `False`, consistency of `org_id` will only be enforced if both are present. If either are missing, the trace will be continued. + +The client's organization ID is extracted from the DSN or can be set with the `org_id` option. +If the organization IDs do not match, the SDK will start a new trace instead of continuing the incoming one. +This is useful to prevent traces of unknown third-party services from being continued in your application. + + + + + +An optional organization ID for your Sentry project. + +The SDK will try to extract the organization ID from the DSN. If it cannot be found, or if you need to override it (if you use Relay or self-hosted), +you can provide the ID with this option. + +The organization ID is used for features like strict trace continuation. + + + An optional list of functions that should be set up for tracing. For each function in the list, a span will be created when the function is executed.