9.27.0 creates Spans for outgoing requests to Sentry (reproduct in Next.js SDK)

[HazAT]

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

SDK Version

9.27.0

Framework Version

Next

Link to Sentry event

No response

Reproduction Example/SDK Setup

Steps to Reproduce

Just make a request

Expected Result

No Span

Actual Result

One Span

[mydea]

Update: vercel/next.js#81063

[mydea]

This happens in the following circumstances:

• In edge environment
• While running in dev

The reason is that locally the edge environment is only "simulated" I suppose, so stuff from the node environment bleeds into it, in this case the diagnostics channels of fetch. Not sure how we can fix this on our end, we'll probably do some band-aid instead.

[mydea]

Final update: We decided to do nothing here, as we cannot reliably detect this. This should ideally be fixed at Next side, other than this it does not affect deployed apps anyhow so the actual impact should be small.