Skip to content

docs: Add strict trace continuation for Apple#17140

Open
antonis wants to merge 2 commits intomasterfrom
docs/strict-trace-continuation-apple
Open

docs: Add strict trace continuation for Apple#17140
antonis wants to merge 2 commits intomasterfrom
docs/strict-trace-continuation-apple

Conversation

@antonis
Copy link
Copy Markdown
Contributor

@antonis antonis commented Mar 26, 2026

DESCRIBE YOUR PR

Add documentation for the strictTraceContinuation and orgId options for the Apple (Cocoa) SDK.

Changes:

  • options.mdx — Add strictTraceContinuation and orgId option descriptions to the Apple SDK configuration options page
  • apple.mdx — Add strict trace continuation section to the Apple distributed tracing guide with Swift code examples

Related SDK PR: getsentry/sentry-cocoa#7705

IS YOUR CHANGE URGENT?

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

⚠️ Should be merged after getsentry/sentry-cocoa#7705 is released

PRE-MERGE CHECKLIST

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 26, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
develop-docs Ready Ready Preview, Comment Apr 8, 2026 8:50am
sentry-docs Ready Ready Preview, Comment Apr 8, 2026 8:50am

Request Review

Copy link
Copy Markdown
Contributor

@itaybre itaybre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a small comment

By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the responses are from a third-party service,
as it can lead to unwanted traces, increased billing, and skewed performance data.

To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks incoming trace information and only continues the trace if it belongs to the same Sentry organization.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks incoming trace information and only continues the trace if it belongs to the same Sentry organization.
To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks incoming trace information and *only* continues the trace if it belongs to the same Sentry organization.

Should we make the only more noticeable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants