Skip to content

Add Option to ignore mark and measure spans #16441

@Lms24

Description

@Lms24

Problem Statement

Today, the browserTracingIntegration always emits spans for performance.mark() as well as performance.measure() spans. However, there are some reasons as to why users don't always want these spans:

  • some extensions (e.g. grammarly) or libraries (e.g. Sentry 😅) emit these entries on their own which are not really useful data points for our users.
  • In some cases, these 3rd-party-emitted values even led to skewing of the entire trace duration because the duration was set incorrectly
  • ultimately, these spans increase user quota and with our recent move away from dropping individual spans retroactively, there's no convenient way for users to filter these out.

Solution Brainstorm

Analogously to #16389 for resource spans, we should expose an option to ignore mark and measure spans.

Metadata

Metadata

Assignees

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions