Outgoing Sentry request on every Next.js API invocation

[kennethkeim]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

After deploying to Vercel today, I noticed in the logs that Sentry is making a request on every request. Prior to today's deployment this was not happening. I had just upgraded from @sentry/nextjs version ^9.44.0 to ^10.0.0 with the deployment so I reverted that and re-deployed with V9 but the issue is still happening.

My traces sample rate is set to 0 on client, server, and edge configurations.

I'm not seeing any errors in the Vercel dashboard or Sentry, and the responses are all served successfully, so the request should not be related to errors being reported.

Expected Result

Sentry does not send network requests if tracing is disabled and no errors are thrown

Actual Result

Sentry is making 1-2 network requests for every request to my API endpoint

Product Area

Ingestion and Filtering

Link

No response

DSN

https://26fc90d7c3681ba580bc9a4a505346a5@o423426.ingest.us.sentry.io/4507945506504704

Version

9.44.0

[linear]

ENG-4735 Outgoing Sentry request on every Next.js API invocation

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[kennethkeim]

I'm now consistently seeing 2 outgoing requests on every request to my endpoint. There's no errors showing up in the Sentry Dashboard. I've also verified no errors are coming through the beforeSend() - I added console logs to verify this.

[kennethkeim]

Ok turns out I'd done multiple phases of dependency upgrades and the last working version was actually 9.14.0 (not 9.44.0 as mentioned in description). I went back to 9.14 and there are no more extra network requests by Sentry. I will stay on this version until this issue is cleared up.

[linear]

JS-833 Outgoing Sentry request on every Next.js API invocation

[Lms24]

Hey @kennethkeim apologies for the delayed response but this issue only made it to our repo today. What you might be seeing are session or "client report" envelope requests.

• session aggregate envelopes count the number of successful or failed requests on the server-side. Not really intuitive but they power our Release Health feature
• client reports provide some metadata if spans or errors were dropped rather than sent, including reasons as to why.

Can you inspect the request body through vercel? If we can take a look at the envelope body we can confirm my suspicion

You can set the following SDK config to disable session envelopes and client reports:

Sentry.init({
  sendClientReports: false,
  integrations: [ Sentry.httpIntegration({ trackIncomingRequestsAsSessions: false }) ]
})

and check if the requests stop.

Let me know if this helps!

[kennethkeim]

@Lms24 I can't see the outgoing request body in Vercel, no. I just tried your suggestion and it worked, thanks a lot! I had to remove the http integration from my Sentry Edge config since it threw an error about it not being supported there.

I do have to ask... should a minor version bump really introduce new network requests? I had endpoints that went from an execution time of ~40 ms to ~120 ms. It didn't seem like the roundtrip from the browser's perspective was taking longer though, so maybe Sentry was using after() to send the network requests after my response had been sent?