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

[v8] Replace custom BrowserTracing routing instrumentations #10387

Closed
9 tasks done
Tracked by #9508
mydea opened this issue Jan 29, 2024 · 0 comments
Closed
9 tasks done
Tracked by #9508

[v8] Replace custom BrowserTracing routing instrumentations #10387

mydea opened this issue Jan 29, 2024 · 0 comments

Comments

@mydea
Copy link
Member

mydea commented Jan 29, 2024

In v7, new BrowserTracing() accepts a custom routingInstrumentation. We use this in a few places.
The replacement browserTracingIntegration() does not accept this anymore (as it is tightly tied to transactions). Instead, this needs to be refactored to a new format using utility methods to start pageload/transaction spans.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants