Repository navigation
No Server Spans or Profiles when using nodeProfilingIntegration on Vercel #15949
Closed as not planned
Description
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
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
- Load product page
- 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
Reacted by Roey D. Chasman
Metadata
Metadata
Assignees
Projects
- Status
Activity
[-]nodeProfilingIntegration Preventing Server Spans on Vercel[/-][+]nodeProfilingIntegration Preventing Server Spans and Profiles on Vercel[/+][-]nodeProfilingIntegration Preventing Server Spans and Profiles on Vercel[/-][+]No Server Spans or Profiles when using nodeProfilingIntegration on Vercel[/+]Lms24 commentedon Apr 2, 2025
Thx for filing @landenai!
It seems like
dbspans 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
nodeProfilingIntegrationand deploying to vercel, do we getdbspans again?rchasman commentedon Apr 10, 2025
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.
Lms24 commentedon Apr 11, 2025
Hey @rchasman it depends a bit on which library you're using (we have auto instrumentation for
pg,mysql,mysql2,ioredis,redisand Prisma). Here's a full overviewTo debug this, can you help us out with debug logs I asked for above? Also, would appreciate a minimal reproduction on the latest SDK version. Thanks!
mydea commentedon May 7, 2025
Why was this issue closed?
This issue hasn't been touched recently and no longer seems relevant.
Hence, we're closing it to maintain a clean and transparent backlog.
Please feel free to leave a comment if you think this issue should be reopened.