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.

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

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

Closed
Prev Previous commit
Next Next commit
add session logic
  • Loading branch information
philipphofmann committed Jun 6, 2024
commit 3a70e7b8586df9f8ed3ed12a3af844dd4813260f
6 changes: 5 additions & 1 deletion text/0136-mobile-tracing-without-performance-v-2.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,11 @@ starfish module uses. Whenever the screen name changes automatically or with a y
[manual API](https://www.notion.so/sentry/Specs-Screens-API-084d773272f24f57aeb622c07619264e),
mobile SDKs must renew the `traceId` of the `PropagationContext`. The screen load transaction
and subsequent events on the same screen must use the same `traceId`. When the app moves to the
background, mobile SDKs also update the `traceId` of the PropagationContext.
foreground after being in the background for longer than 30 seconds, which is the same approach
mobile SDKs use for determining the end of a session, mobile SDKs renew the `traceId` of the
PropagationContext. If the app stays in the background for shorter or equal to 30 seconds,
mobile SDKs must not renew the `traceId` of the PropagationContext when the app moves again to
the foreground.

### Pros <a name="option-1-pros"></a>

Expand Down