Problem Statement
Customers want Sessions, without the replay aspect. see this related GH Issue about that:
getsentry/sentry#72929
Customers do not want the full Session Replay due to legal concerns (despite showing the Privacy controls, some still refuse to use it) as well as Negative Overhead on their app
Other vendors have sessions.
Hard to find all the span-metrics from a 'session' if the trace you're looking at doesn't have a pointer to the next trace.
Solution Brainstorm
Two parts to the solution.
-
SDK option for ignoring the session replay visual. Minimize/hide the screen preview and default to the Traces tab, present that instead.
-
All the Traces and Spans don't need a nextSpan or nextTransaction property, because they'll be linked to the SessionReplay, which already has all the other spans+transactions linked.

Problem Statement
Customers want Sessions, without the replay aspect. see this related GH Issue about that:
getsentry/sentry#72929
Customers do not want the full Session Replay due to legal concerns (despite showing the Privacy controls, some still refuse to use it) as well as Negative Overhead on their app
Other vendors have sessions.
Hard to find all the span-metrics from a 'session' if the trace you're looking at doesn't have a pointer to the next trace.
Solution Brainstorm
Two parts to the solution.
SDK option for ignoring the session replay visual. Minimize/hide the screen preview and default to the Traces tab, present that instead.
All the Traces and Spans don't need a nextSpan or nextTransaction property, because they'll be linked to the SessionReplay, which already has all the other spans+transactions linked.