Skip to content

Stop emitting browser mark and measure spans by default #22352

Description

@Lms24

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:

  1. (low effort) build a "match-all" regexp as a default for ignorePerformanceApiSpans
  2. (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

Metadata

Metadata

Assignees

No one assigned

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions