Repository navigation
Conversation
Our own transport sends with tracing suppressed, but another SDK in the same process does not share that scope. On Next.js, the Edge Runtime SDK runs in a sandbox inside the Node.js process and sends with undici `fetch`, so the Node.js SDK created `http.client` spans for these requests. Skip requests to the client's DSN or tunnel in the undici and `http` client instrumentation, like the `fetch` integration already does. This replaces the Next.js `beforeSampling` drop, which only applied to root spans and was no longer enforced. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Lms24
changed the title
undici fetch
Contributor
size-limit report 📦
|
Lms24
changed the title
undici fetchundici fetch and node:http
Member
Author
|
bugbot review |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 56f0f4b. Configure here.
`@sentry/node` cannot instrument `fetch` on Bun and Deno, so the fetch suite joins the other fetch suites in their exclude lists. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Lms24
marked this pull request as ready for review
October 16, 2026 10:05
This branch has not been deployed
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
1 participant
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.
This PR fixes a bug where undici and
httpclient instrumentation created spans for requests to the sentry ingest endpoint. We now skip requests to the client's DSN or tunnel viaisSentryRequestUrl, like we already do in ourfetchintegrations (node, cloudflare, vercel edge). This checks the raw URL, so it works regardless ofdataCollection.urlQueryParams.This surfaced in NextJS while working on #25386, where apparently we'd start spans in standalone (node, preview, dev) Next environments. Based on Claude research this happened because of NextJS sandboxing the edge runtime requests in a sub process of the Node process and our instrumentation catching those calls in both, the sandbox and the main process. The fix therefore replaces the Next.js
beforeSamplingdrop for these spans, which only applied to root spans and has accidentally not been enforced sinceSentrySamplerwas removed.