-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
docs(tracing): Add docs for Previous and Next trace #13406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
|
||
### Previous and Next Traces | ||
|
||
As users interact with the application, they generate multiple traces. For example, when a user loads a page in their browser and then navigates to another page, this creates two separate traces: one for the initial pageload and another for the subsequent navigation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the second paragraph starts with "linked traces", I think we need to introduce this a bit earlier
(feel free to go with your own version as you see fit)
As users interact with the application, they generate multiple traces. For example, when a user loads a page in their browser and then navigates to another page, this creates two separate traces: one for the initial pageload and another for the subsequent navigation. | |
As users interact with the application, they generate multiple traces. For example, when a user loads a page in their browser and then navigates to another page, this creates two separate traces: one for the initial pageload and another for the subsequent navigation. Sentry will link these traces for you. |
Bundle ReportChanges will increase total bundle size by 198 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-server-cjsAssets Changed:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding, looks good!
Co-authored-by: Alex Krawiec <[email protected]>
* 'master' of https://github.com/getsentry/sentry-docs: (131 commits) refactor: migrate Golang and related guides to inline product options syntax (#13413) refactor: migrate DotNet sdks to inline product options syntax (#13415) add note of the switch sdk (#13431) Update spelling in examples.mdx (#13378) ref(replay): clarify web & mobile distinction in product docs (#13447) fix(java): fix `RestTemplate` auto-instrumentation guide (#13236) refactor: migrate Python and related guides to inline product options syntax (#13412) Unreal: Document and add `SendDefaultPii = true` to onboarding docs (#13435) docs(tracing): Add docs for Previous and Next trace (#13406) docs(js): Create Svelte Quick Start guide (#13387) Update Profiling SDK version number for iOS/macOS (#13429) remove note that workflow notifications alert on new feedback (#13384) fix(dart): 404 link (#13430) feat(Godot): Update options screenshot on the landing page (#13428) add senddefaultpii to powershell (#13426) powershell senddefaultpii landing page (#13427) chore: update powershell min version requirement (#13425) docs(replays): add count_traces to searchable properties (#13422) docs(js): Add `sendDefaultPii: true` to all init calls (#13408) docs(dotnet): Add `SendDefaultPii = true` option (#13423) ...
* docs(tracing): Add docs for Previous and Next trace * add additional sentence * Update docs/concepts/key-terms/tracing/trace-view.mdx Co-authored-by: Alex Krawiec <[email protected]> --------- Co-authored-by: Alex Krawiec <[email protected]>
DESCRIBE YOUR PR
Adds short docs for Linked Trace navigation.
closes #13400
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: