browserTracingIntegration today emits mark and measure spans by default. These come from the respective browser performance.(mark|measure) APIs.
Spans generated from them are often noisy because third party scripts and extensions make use of those marks (e.g. Grammarly) that then trickle into users' traces.
There are two directions we can take this for v11:
- (low effort) build a "match-all" regexp as a default for
ignorePerformanceApiSpans
- (medium effort) extract them out into their own integration and tell users who want these spans to use the integration explicitly. If we either way are fine with not sending these spans by default, this does not interfere with our plans for splitting up
browserTracingIntegration but we'll frontload this specific change and make the new integration completely independent of browserTracing.
Option two would save some bundle size
browserTracingIntegrationtoday emitsmarkandmeasurespans by default. These come from the respective browserperformance.(mark|measure)APIs.Spans generated from them are often noisy because third party scripts and extensions make use of those marks (e.g. Grammarly) that then trickle into users' traces.
There are two directions we can take this for v11:
ignorePerformanceApiSpansbrowserTracingIntegrationbut we'll frontload this specific change and make the new integration completely independent of browserTracing.Option two would save some bundle size