feat(browser)!: Extract interaction spans into new interactionsIntegration - #23295
Merged
Conversation
Member
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
size-limit report 📦
|
msonnb
force-pushed
the
ms/interactions-integration
branch
from
August 12, 2026 08:16
fb1b1ca to
f64077e
Compare
msonnb
marked this pull request as ready for review
August 12, 2026 08:20
msonnb
requested review from
Lms24 and
logaretm
and removed request for
a team
August 12, 2026 08:20
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Contributor
1 similar comment
Contributor
msonnb
force-pushed
the
ms/interactions-integration
branch
from
August 24, 2026 07:30
718ec12 to
b695d9d
Compare
andreiborza
self-requested a review
August 24, 2026 08:52
…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>
msonnb
force-pushed
the
ms/interactions-integration
branch
from
August 24, 2026 11:13
b695d9d to
9b4b744
Compare
andreiborza
approved these changes
Aug 24, 2026
| Sentry.init({ | ||
| traceLifecycle: 'static', | ||
| dsn: 'https://public@dsn.ingest.sentry.io/1337', | ||
| integrations: [Sentry.browserTracingIntegration({ enableLongTask: false })], |
Member
There was a problem hiding this comment.
q: why did we add this option?
Member
Author
There was a problem hiding this comment.
was a leftover from before. removed.
Lms24
approved these changes
Aug 24, 2026
Comment on lines
+99
to
+101
| * Captures user interactions as spans. | ||
| * | ||
| * Clicks that happen outside of an in-progress pageload or navigation start an idle `ui.action.click` span, |
Member
There was a problem hiding this comment.
Suggested change
| * Captures user interactions as spans. | |
| * | |
| * Clicks that happen outside of an in-progress pageload or navigation start an idle `ui.action.click` span, | |
| * Captures user interactions as spans. | |
| * | |
| * Important: This integration is considered experimental and might lead to noisy spans. Use at your own risk. | |
| * | |
| * | |
| * Clicks that happen outside of an in-progress pageload or navigation start an idle `ui.action.click` span, |
| function trackRoute(span: Span): void { | ||
| const { name, attributes } = spanToJSON(span); | ||
| latestRoute.name = name; | ||
| latestRoute.source = attributes[SEMANTIC_ATTRIBUTE_SENTRY_SOURCE] as TransactionSource | undefined; |
Member
There was a problem hiding this comment.
We should read both source attributes (from conventions) for now but #23368 will likely make SENTRY_SOURCE obsolete in a bit.
Suggested change
| latestRoute.source = attributes[SEMANTIC_ATTRIBUTE_SENTRY_SOURCE] as TransactionSource | undefined; | |
| latestRoute.source = (attributes[SENTRY_SOURCE] || attributes[SENTRY_SEGMENT_NAME_SOURCE]) as TransactionSource | undefined; |
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 317c345. Configure here.
JPeer264
pushed a commit
that referenced
this pull request
Aug 25, 2026
…ration` (#23295) ## What This extracts interaction spans into a new opt-in (standalone) `interactionsIntegration`. ```js // before Sentry.browserTracingIntegration({ _experiments: { enableInteractions: true } }); // after [Sentry.browserTracingIntegration(), Sentry.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 --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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