Sentry creates separate otel context for dynamic pages when using @vercel/otel

[adam187]

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

8.17.0

Framework Version

next latest

Link to Sentry event

No response

SDK Setup/Reproduction Example

https://github.com/adam187/nextjs-sentry-otel-example

Steps to Reproduce

1. yarn install
2. yarn build
3. yarn start
4. curl 'http://localhost:3000'

Expected Result

All otel spans should have same trace id for single request.

Actual Result

Sentry creates own isolated scope that cause having spans from single splitted into two separate traces.

This is problematic since you can't view full trace for a single request.

[adam187]

Looks like it could be related to #11625

[lforst]

Hi, I am trying to better understand your desired outcome. What do traces look for you, and what would you like them to look like?

[adam187]

Hi, I am trying to better understand your desired outcome. What do traces look for you, and what would you like them to look like?

Sorry for late reply.

The desired outcome would be to have all spans from single request assigned to same trace id.
Now Sentry creates own context so all spans created by sentry and within sentry context are not assigned to original trace.

For us it's problematic since we can't see full trace by original trace id.

[chargome]

Hi @adam187, I talked with @lforst and there are a few things to unpack:

• In order to use Sentry with a custom OTEL instrumentation you need to follow some additional steps: https://docs.sentry.io/platforms/javascript/guides/nextjs/tracing/instrumentation/opentelemetry/#using-a-custom-opentelemetry-setup Make sure to add all of the components like the span processor, the propagator, the context manager and so on!
• We do not pick up OTEL instrumentation from Next.js pages router, because we found that it has a lot of incorrect data (see OpenTelemetry: Improve Span Quality vercel/next.js#64723). For app router, the data emitted by Next.js is accurate.
• Our current recommendation for you, if you are only intending to use Sentry for tracing is to ditch the @vercel/otel package. You will not get much more (if any) good data from it.