No automatic transactions when instrumenting Custom Remix Server

[souredoutlook]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/remix

SDK Version

latest

Framework Version

Remix v2

Link to Sentry event

n/a

SDK Setup

n/a

Steps to Reproduce

1. create a Remix application with a custom express server
2. instrument as described in manual instrumentation
3. load the application from the browser
4. no http.server transactions are produced

Expected Result

loading the index root should produce an http.server transaction

Actual Result

After stepping through the code it looks like we are wrapping the remix server and then not wrapping the request handler as isRequestHandlerWrapped is evaluating to true despite no transactions being produced automatically from the back-end.

(Breakpoint was set at this location here:

sentry-javascript/packages/remix/src/utils/instrumentServer.ts

Line 528 in b6a7cef

isRequestHandlerWrapped = true;

)

The workaround was to import Sentry in entry.server.ts from @sentry/node and call Sentry.init() as usual

[onurtemizkan]

A wrapped request handler will not have transactions if there is no client available in the context of that request handler, and this might be the problem.

The workaround was to import Sentry in entry.server.ts from @sentry/node and call Sentry.init() as usual

So as I understand you don't get http.server transactions when Sentry.init is imported from @sentry/remix but it's fine when it's from @sentry/node, is that correct?

If that's the case, could you try using Sentry.init from @sentry/remix with debug: true and check the logs for any warnings, specifically "SDK already initialized"?

[souredoutlook]

Hey @onurtemizkan - we debugged the issue today with @AbhiPrasad and the end-user. I'll send over a video of the stepping through the repro with breakpoints shortly.

FWIW we did not observe the "SDK already initialized" message at any time. And custom instrumentation did work as expected, however the request handler wrapper did not.