Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
feat(python): Add strict_trace_continuation and org_id
  • Loading branch information
sl0thentr0py committed Dec 1, 2025
commit 092ade65df69697f0780f66847cbe08c7561680b
23 changes: 23 additions & 0 deletions docs/platforms/python/configuration/options.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -378,6 +378,29 @@ If `trace_propagation_targets` is not provided, trace data is attached to every

</SdkOption>

<SdkOption name="strict_trace_continuation" type='boolean' defaultValue='False'>

If set to `True`, the SDK will only continue a trace if the organization ID of the incoming trace found in the
`baggage` header matches the organization ID of the current Sentry client.

The client's organization ID is extracted from the DSN or can be set with the <PlatformLink to={'/configuration/options#org_id'}>`org_id` option</PlatformLink>.

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.

</SdkOption>

<SdkOption name="org_id" type='str'>

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 <PlatformLink to="/configuration/options#strict_trace_continuation">strict trace continuation</PlatformLink>.

</SdkOption>

<SdkOption name="functions_to_trace" type='list[str]' defaultValue='[]'>

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.
Expand Down
Loading