ref(node): Refactor http instrumentation away from OTEL

[mydea]

Refactors the outgoing HTTP instrumentation so it no longer relies on OpenTelemetry's InstrumentationBase/InstrumentationNodeModuleDefinition machinery. Outgoing requests (breadcrumbs, spans, and trace-header propagation) are now handled directly by Sentry code, using Node's node:http client diagnostics channel where available and falling back to monkey-patching on older runtimes.

What changed

• node-core: SentryHttpInstrumentation → instrumentHttpOutgoingRequests(). The core logic is now a plain function instead of an OTEL instrumentation class. On Node 22.12+ (and 23.2+/24+) it subscribes to the node:http client diagnostics channel — and is safely re-subscribable, so calling it again swaps in the latest options. On older runtimes it falls back to monkey-patching. The SentryHttpInstrumentation class is kept as a thin, deprecated wrapper for backwards compatibility.

• core: new monkey-patch strategy — patch ClientRequest.prototype.onSocket instead of the module's request/get exports. Every outgoing request ultimately constructs a ClientRequest and calls onSocket on the shared prototype, so patching it reaches consumers regardless of how the module was imported — including immutable ESM namespace bindings (import * as http / import { request }) that can't be monkey-patched otherwise. onSocket runs synchronously during request setup (before headers flush, in the caller's async context), so trace headers are still injectable and spans are parented correctly. https reuses http's ClientRequest, so a single patch covers both, and inherited-prototype double-patching is guarded against. Instrumentation errors are swallowed so they can never break the underlying request.

• core: HttpExport type reshaped to expose the ClientRequest constructor (HttpClientRequestConstructor) rather than request/get.

• node & node-corehttpIntegration wiring now points instrumentSentryHttp at instrumentHttpOutgoingRequests directly (via Object.assign) instead of generateInstrumentOnce + new SentryHttpInstrumentation. instrumentHttpOutgoingRequests is now exported from node-core.

• Docs: clarified the OutgoingHttpRequestInstrumentationOptions option comments to match actual behavior — notably that ignoreOutgoingRequests skips the request entirely (no breadcrumb, no span, no trace propagation), and that the outgoing hooks only fire when spans are actually created.

• Tests / test-utils: updated client-patch tests for the new strategy and gave createTestServer an explicit TestServer return type.

Closes#20902

[github-actions]

size-limit report 📦

⚠️Warning: Base artifact is not the latest one, because the latest workflow run is not done yet. This may lead to incorrect results. Try to re-run all tests to get up to date results.

Path	Size	% Change	Change
@sentry/browser	27.59 kB	-	-
@sentry/browser - with treeshaking flags	26.03 kB	-	-
@sentry/browser (incl. Tracing)	46.27 kB	-	-
@sentry/browser (incl. Tracing + Span Streaming)	48.03 kB	-	-
@sentry/browser (incl. Tracing, Profiling)	51.03 kB	-	-
@sentry/browser (incl. Tracing, Replay)	85.56 kB	-	-
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	75.17 kB	-	-
@sentry/browser (incl. Tracing, Replay with Canvas)	90.26 kB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback)	102.91 kB	-	-
@sentry/browser (incl. Feedback)	44.76 kB	-	-
@sentry/browser (incl. sendFeedback)	32.38 kB	-	-
@sentry/browser (incl. FeedbackAsync)	37.51 kB	-	-
@sentry/browser (incl. Metrics)	28.67 kB	-	-
@sentry/browser (incl. Logs)	28.91 kB	-	-
@sentry/browser (incl. Metrics & Logs)	29.59 kB	-	-
@sentry/react	29.38 kB	-	-
@sentry/react (incl. Tracing)	48.53 kB	-	-
@sentry/vue	33.03 kB	-	-
@sentry/vue (incl. Tracing)	48.16 kB	-	-
@sentry/svelte	27.61 kB	-	-
CDN Bundle	30 kB	-	-
CDN Bundle (incl. Tracing)	48.26 kB	-	-
CDN Bundle (incl. Logs, Metrics)	31.57 kB	-	-
CDN Bundle (incl. Tracing, Logs, Metrics)	49.57 kB	-	-
CDN Bundle (incl. Replay, Logs, Metrics)	70.81 kB	-	-
CDN Bundle (incl. Tracing, Replay)	85.73 kB	-	-
CDN Bundle (incl. Tracing, Replay, Logs, Metrics)	87.04 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback)	91.55 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics)	92.83 kB	-	-
CDN Bundle - uncompressed	89.35 kB	-	-
CDN Bundle (incl. Tracing) - uncompressed	145.99 kB	-	-
CDN Bundle (incl. Logs, Metrics) - uncompressed	94.05 kB	-	-
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed	149.96 kB	-	-
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed	218.75 kB	-	-
CDN Bundle (incl. Tracing, Replay) - uncompressed	265.16 kB	-	-
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed	269.12 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	278.86 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed	282.81 kB	-	-
@sentry/nextjs (client)	50.94 kB	-	-
@sentry/sveltekit (client)	46.68 kB	-	-
@sentry/core/server	78.33 kB	-0.07%	-52 B 🔽
@sentry/core/browser	64.74 kB	-	-
@sentry/node-core	62.72 kB	-0.78%	-491 B 🔽
@sentry/node	124.6 kB	-0.11%	-129 B 🔽
@sentry/node (incl. diagnostics channel injection)	130.84 kB	-0.11%	-135 B 🔽
@sentry/node/import (ESM hook with diagnostics-channel injection)	69.95 kB	-	-
@sentry/node/light	50.72 kB	-	-
@sentry/node - without tracing	74.05 kB	-1.03%	-764 B 🔽
@sentry/aws-serverless	85.5 kB	-0.12%	-97 B 🔽
@sentry/cloudflare (withSentry) - minified	181.68 kB	-	-
@sentry/cloudflare (withSentry)	449.39 kB	-	-

View base workflow run

[timfish]

Oh this is a nice bonus!

[isaacs]

This is a huge improvement! Very good direction found by the clanker ;)

However, onSocket doesn't play nice with http.Agent if sockets are being managed. I suggested two other approaches we could use (either patch all 3 of the header-sending public methods, or the single internal _storeHeader method).

[cursor]

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.}

^{Reviewed by Cursor Bugbot for commit 60a3f07. Configure here.}

[JPeer264]

q: Is this part of the PR? Pretty sure it is, just wondering why we didn't need it before. And if we need it we can remove the disable-next-line above, unfortunately oxlint, doesn't complain if the rule doesn't apply 😢

[mydea]

only tangentially, noticed that this lead to squiggly lines in tests that I touched here - imho something seems not properly set up for node integration tests, need to look at this in a follow up :) and will remove the ignore line!

[JPeer264]

q: Because this got moved, should we add a v11 todo? As node-core will be merged in v11 this might be a good time to revisit already

[mydea]

I think no need for a todo comment here specifically, because we'll need to revisit this anyhow because node-core will go away so all of this will necessarily receive attention :D

[isaacs]

Some nits on the JSDoc comments, just combing through the deprecated stuff, but all the functional problems seem to be addressed 🥇