deno: denoServeIntegration lacks the incoming request options that denoHttpIntegration has #25492

Deno has two server integrations.

denoHttpIntegration covers node:http servers. denoServeIntegration covers Deno.serve, which is the native server and the one most Deno apps use.

denoServeIntegration takes only two options: maxRequestBodySize and the deprecated ignoreStatusCodes. denoHttpIntegration takes many more options for incoming requests. So a user who moves from node:http to Deno.serve loses control over what the SDK captures.

The option a user is most likely to need is ignoreRequestBody. Today a Deno.serve user can only turn body capture on or off for all routes. They cannot skip a health check, a file upload, or a route that receives secrets. Node (httpIntegration), Cloudflare (httpServerIntegration) and Deno's own denoHttpIntegration all have this option.

Proposed options

Use the same names and semantics as denoHttpIntegration. Callbacks get the web Requestinstead of a node:http IncomingMessage, which matches Cloudflare's httpServerIntegration.

Needs a decision: sessions and sessionFlushingDelayMS

denoHttpIntegration records request sessions (#22888 turned them on), but Deno.serve does not. So release health for most Deno apps shows no request sessions. The shared helper recordRequestSession in @sentry/core/server waits for a node:http response close event. Deno.serve needs a small adapter, or the helper needs a callback form. This is bigger than the other options and could be its own issue.

Implementation notes

• All the code is in packages/deno/src/integrations/deno-serve.ts and packages/deno/src/wrap-deno-request-handler.ts.
• The wrapper already reads maxRequestBodySize from the integration instance through client.getIntegrationByName('DenoServe'). New options can be read the same way.
• Check ignoreRequestBody in the wrapper next to the existing request.method !== 'GET' check, before captureBodyFromWinterCGRequest. The request body can only be read once, so the check must run before the SDK clones or reads it.
• Cloudflare's captureIncomingRequestBody inpackages/cloudflare/src/integrations/httpServer.ts already does this for a web Request. Consider moving it to @sentry/core so both runtimes share it.
• Leave ignoreStatusCodes as it is. It is deprecated, and it only works with traceLifecycle: 'static'.

Tests

• Unit tests in packages/deno/test/deno-serve.test.ts for each option.
• For ignoreRequestBody, check that the event has no request.data when the callback returns true, and that the handler can still read the body.
• For ignoreIncomingRequests and ignoreStaticAssets, check that no server span is sent and that a thrown error is still captured.

Related

• Bun.serve (bunServerIntegration) has the same gap. It takes only maxRequestBodySize. The same option set could apply there, in the same issue or a separate one.
• Deno's export surface is narrower than Cloudflare's #23896 / Deno's export surface is narrower than Cloudflare's #23896 deferred porting Cloudflare's httpServerIntegration to Deno. Adding these options to denoServeIntegration gives Deno the same features without a second integration that configures the same thing.