Skip to content
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.

Sign up for GitHub

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

Jump to bottom

rfc(decision): Mobile - Tracing Without Performance V2 #136

Closed
wants to merge 9 commits into from
Closed

rfc(decision): Mobile - Tracing Without Performance V2 #136

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
313a0a0
rfc(decision): Mobile - Tracing Without Performance V2
philipphofmann Jun 4, 2024
27c44c4
first version
philipphofmann Jun 4, 2024
a68b563
add cons
philipphofmann Jun 4, 2024
e3be25a
Update text/0136-mobile-tracing-without-performance-v-2.md
philipphofmann Jun 5, 2024
3a70e7b
add session logic
philipphofmann Jun 6, 2024
9c252cc
Update text/0136-mobile-tracing-without-performance-v-2.md
philipphofmann Jun 10, 2024
fddeeaa
Update text/0136-mobile-tracing-without-performance-v-2.md
philipphofmann Jun 10, 2024
764196a
spans across screens
philipphofmann Jun 10, 2024
cd840eb
add route to the title
philipphofmann Jun 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Prev Previous commit
Next Next commit
Update text/0136-mobile-tracing-without-performance-v-2.md 
Co-authored-by: Roman Zavarnitsyn <[email protected]>
  • Loading branch information
@philipphofmann @romtsn
philipphofmann and romtsn committed Jun 10, 2024
commit fddeeaa2e6a7185b0b88a4579574938bd8701fae
2 changes: 1 addition & 1 deletion text/0136-mobile-tracing-without-performance-v-2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ On mobile, most users interact purely with the static API, which holds a referen
Hub and Scope. Therefore, mobile SDKs create a `PropagationContext` with `traceId` and `spanId`
during initialization, and these usually persist for the entire lifetime of the app. Mobile
SDKs prefer the `traceID` of transactions bound to the scope over the `PropagationContext`. So
when performance is disabled, or no transition is bound to the scope, mobile SDKs use the same
when performance is disabled, or no transaction is bound to the scope, mobile SDKs use the same
`traceId` and `spanId` for all captured events. This can lead to traces with hundreds of
unrelated events confusing users. JS addressed this recently by updating the `PropagationContext`
based on routes, see [Ensure browser traceId lifetime works as expected](https://github.com/getsentry/sentry-javascript/issues/11599).
Expand Down