Uh oh!
There was an error while loading. Please reload this page.
fix(nextjs): Skip tracing for tunnel requests - #19861
Conversation
size-limit report 📦
|
Uh oh!
There was an error while loading. Please reload this page.
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.
Uh oh!
There was an error while loading. Please reload this page.
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨
Bug Fixes 🐛Deps
Other
Internal Changes 🔧
🤖 This preview updates automatically when you update the PR. |
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|

Fix Next.js tunnel route span filtering by extending
dropMiddlewareTunnelRequeststo also dropBaseServer.handleRequestspans that match the tunnel path, replacing a fragile transaction-name string comparison in the event processor with the early, attribute-basedTRANSACTION_ATTR_SHOULD_DROP_TRANSACTIONmechanism already used for middleware and fetch spans.closes https://linear.app/getsentry/issue/JS-1952/nextjs-automatically-filter-tunnel-route-spans
closes#19840