Description
Problem Statement
Currently, the current and isolation scope's propagationContext stays the same across multiple page navigations. This leads to a couple of unintended problems:
- One trace is carried on infinitely as longs as a user is using an app without closing the tab or reloading it
- This leads to very long, convoluted traces where transactions are collected that have nothing (little) to do with each other in practice.
- The same goes for outgoing requests when performance monitoring is not active ("tracing w/o performance").
Solution Brainstorm
In an effort to alleviate these symptoms and to reduce the logical duration of one trace, we'll reset the propagationContext whenever a navigation occurs. This won't solve all long and convoluted traces but at least will cut them down significantly for applications where some kind of client-side routing is performed. Apps that use no routing at all will still "suffer" from large traces but for now, we accept that.
Propagation context resetting will happen roughly wherever we update the scope's transactionName (see #10846).