No Server Spans or Profiles when using nodeProfilingIntegration on Vercel

[landenai]

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/nextjs

SDK Version

9.10.1

Framework Version

Next 15.0.1

Link to Sentry event

https://demo.sentry.io/discover/trace/f1eebb3564204653b318bf254d6bedfa/?dataset=transactions&field=title&field=project&field=user.display&field=timestamp&name=All%20Errors&node=txn-ab4a4d9e58844679b25971740d7a78e0&project=4508968158429184&query=&queryDataset=transaction-like&sort=-timestamp&source=discover&statsPeriod=7d&timestamp=1743522159&yAxis=count%28%29

Reproduction Example/SDK Setup

With nodeProfilingIntegration is enabled in the Next.js SDK, we don't get all the server spans that we do when it is disabled. Additionally there aren't any profiles coming in from the SDK. This behavior is only observed on Vercel, localhost works as expected. (Link to how the above trace should look)

Steps to Reproduce

1. Load product page
2. Go to Pageload transaction in Sentry

Expected Result

Trace has all server spans and profiles attached

Actual Result

Trace does not have all server spans and no profiles attached

[Lms24]

Thx for filing @landenai!

It seems like db spans are missing in the trace with profiling. Which makes me think that the Otel postgres instrumentation isn't patching as expected. Do we have debug logs from the vercel deploy? We can confirm that otel doesn't patch this if we don't find any debug logs around it.

Shot in the dark: This might be related to us detecting ESM vs CJS incorrectly. Again, debug logs can help us out here as we emit a "Running in ESM|CommonJS mode" log after our detection attempt (also worth noting, there's a pending bugfix via #15927).

Last question: when removing nodeProfilingIntegration and deploying to vercel, do we get db spans again?

[rchasman]

I've never gotten db spans with this exact setup and thought it was just a next/sentry limitation. I thought if we wanted spans we would have to instrument them manually.