Navigation spans are started as child spans if experimental interaction spans are used #17450
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/vue -- this might very well be a @sentry/browser issue!
SDK Version
10.5.0
Framework Version
Vue ^3.5.17
Link to Sentry event
Reproduction Example/SDK Setup
Steps to Reproduce
- Enable experimental interaction spans && tracing
- Click button that triggers a navigation
Expected Result
This is the hard part: I don't particularly like the expected result but our current tracing model relies on the fact that navigation spans start a new trace.
So therefore, I'd expect the navigation span to always be a root span, unless we detect it's a navigation.redirect span in which case it must not be a root span. 🥲
The side-effect of this is that the surrounding interaction span will not link directly to the navigation span but maybe we can tackle this separately (This would be a good candidate for increasing interaction span robustness. I just can't find the issue right now). Given that interaction spans are experimental, I don't care too much about this right now though.
Actual Result
The navigation span is started as a child of the ui.interaction.click interaction idle span.
