Description
Hi,
We are using the tracing feature to quickly see all errors during an user session. It worked well, but since the may SDK update, the TraceID is regenerated everytime a scened changes or the user switch focus. It means that we can't easily see all errors during execution at the same time, and it makes debugging for us harder.
We use no transactions, spans or anything, we just want to see quickly all errors that happened during the same execution to have a quick and global idea of what went wrong and when.
(as documentation states : The Sentry SDK regenerates the trace ID whenever the game gains focus or the active scene changes. This creates smaller, more focused trace groups rather than one continuous trace from startup to shutdown, helping you identify truly related errors.)
Would it be possible to have an option at SDK init, that force the same trace ID so we can have one continuous trace from startup to shutdown?
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Status