feat(browser)!: Extract interaction spans into new interactionsIntegration - #23295
feat(browser)!: Extract interaction spans into new interactionsIntegration#23295msonnb wants to merge 3 commits into
interactionsIntegration#23295Conversation
…ration` Interaction spans (`ui.action.click` idle spans and `ui.interaction.click` event-timing spans) are no longer part of `browserTracingIntegration`. They move into a standalone, opt-in `interactionsIntegration`. The experimental `_experiments.enableInteractions` option is removed. As it was the only experimental option, `browserTracingIntegration` no longer accepts an `_experiments` object at all. The `idleTimeout`, `finalTimeout` and `childSpanTimeout` options for interaction spans are configured on the new integration instead of being inherited, using the same defaults. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
bugbot run |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit e5e9450. Configure here.
| }, | ||
| }, | ||
| idleSpanOptions, | ||
| ); |
There was a problem hiding this comment.
Missing origin on idle spans
Medium Severity
startIdleSpan for ui.action.click does not set SENTRY_ORIGIN / sentry.origin. Spans then default to manual, so auto-instrumented interaction idle spans are mis-attributed. Child ui.interaction.click spans already set origin correctly. This violates the PR review rule that every startSpan API call must set a proper span origin (see https://develop.sentry.dev/sdk/telemetry/traces/trace-origin/).
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit e5e9450. Configure here.
size-limit report 📦
|


What
This extracts interaction spans into a new opt-in (standalone)
interactionsIntegration.Why
Interaction idle spans have been experimental since v7. We don't expect to promote them to stable, but they still cost bundle size for every user of
browserTracingIntegration.closes #22353