[isaacs]

Bun.serve took only maxRequestBodySize. A user could not skip body capture or spans for one route, and release health showed no request sessions or crash-free rate for Bun.serve apps. denoServeIntegration got these in #25493 and #25496.

bunServerIntegration now accepts ignoreRequestBody, ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated, onSpanEnd, sessions and sessionFlushingDelayMS. They use the same names and behavior as denoServeIntegration, and the callbacks receive the web Request. The shared ServerRequestOptions check for Bun.serve now lists no unsupported options.

When the SDK skips the span, it still continues the incoming trace, attaches request data and the body, records the session and captures errors. For a streamed response, onSpanEnd and the session end when the stream finishes. A user callback that throws does not fail the request. If ignoreRequestBody throws, the SDK skips the body, so it cannot leak data that the filter was meant to hide.

Three changes in behavior:

• ignoreStaticAssets defaults to true, so GET requests for files such as favicon.ico or *.js no longer create spans.
• spans defaults to the client's tracing configuration, so the integration no longer starts spans when tracing is disabled.
• Errors thrown for OPTIONS and HEAD requests are now captured. These requests also record sessions, as on Node and Deno.

Fixes #25571
Fixes JS-3969

[linear-code]

JS-3969

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7e82d34. Configure here.}