Correct documentation wording on trace propagation #15634
Draft
+6
−6
Conversation
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
|
Cursor Agent can help with this pull request. Just |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
cursor
bot
force-pushed
the
cursor/correct-documentation-wording-on-trace-propagation-claude-4.5-opus-high-thinking-a6c8
branch
from
300f975 to
1dee9f2
Compare
Add note that distributed tracing works automatically, addressing the misconception that "enabling tracing" is required for trace propagation between services. Updated Dart, Flutter, Android, React Native, and Apple platform docs.
cursor
bot
force-pushed
the
cursor/correct-documentation-wording-on-trace-propagation-claude-4.5-opus-high-thinking-a6c8
branch
from
1dee9f2 to
ba84a10
Compare
Bundle ReportChanges will increase total bundle size by 981 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR clarifies the wording around tracing in the Dart, Android, iOS/Apple, and React Native documentation.
The previous text implied that "enabling tracing" was a prerequisite for trace propagation (connecting services), which is not entirely accurate. Trace propagation works automatically. "Enabling tracing" specifically refers to enabling performance monitoring.
The changes clarify that:
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES