docs(rust): Document strict trace continuation options - #18872
Open
szokeasaurusrex wants to merge 1 commit into
Open
docs(rust): Document strict trace continuation options#18872szokeasaurusrex wants to merge 1 commit into
szokeasaurusrex wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Add org_id and strict_trace_continuation to the Rust SDK options page, covering baseline org ID comparison on incoming traces, strict mode behavior, and guidance for self-hosted/Relay setups and SDKs that don't attach org IDs yet. Fixes #18553
szokeasaurusrex
force-pushed
the
docs/rust-strict-trace-continuation
branch
from
July 29, 2026 15:00
0676ae1 to
9a04441
Compare
szokeasaurusrex
marked this pull request as ready for review
July 29, 2026 15:01
alexander-alderman-webb
approved these changes
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Documents the Rust SDK's
org_idandstrict_trace_continuationoptions (shipped in sentry-rust 0.49.0) on the Rust configuration options page.The new entries explain that the SDK compares the incoming
baggagesentry-org_idwith its own organization ID when a transaction starts from incoming headers: mismatched org IDs always start a new trace, and enabling strict trace continuation additionally rejects traces carrying no org ID. An info alert covers org ID configuration (SaaS DSNs need nothing; self-hosted/Relay setups should setorg_idexplicitly), and a warning alert notes that not all SDKs attach org IDs to outgoing traces yet — including the Rust SDK itself — so the option should stay disabled if upstream services use such SDKs.Closes #18553
Closes RUST-254
IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST