Repository navigation
Sentry creates separate otel context for dynamic pages when using @vercel/otel #12907
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
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
- yarn install
- yarn build
- yarn start
- 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.
Metadata
Metadata
Projects
- Status
Activity
adam187 commentedon Jul 13, 2024
Looks like it could be related to #11625
lforst commentedon Jul 15, 2024
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 commentedon Jul 29, 2024
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 commentedon Jul 29, 2024
Hi @adam187, I talked with @lforst and there are a few things to unpack:
@vercel/otelpackage. You will not get much more (if any) good data from it.22 remaining items
lforst commentedon Oct 14, 2024
@csshsh we'll release an update to the SDK very soon that should address all of your concerns. Right now there is no workaround except for disabling
@vercel/otelwhich btw also produces a lot of incorrect data. (see vercel/next.js#70908)csshsh commentedon Oct 14, 2024
Just to avoid misunderstandings, this update to the Sentry SDK will also allow configuring Sentry in a way so it does NOT escape from the next.js tracing?
lforst commentedon Oct 14, 2024
@csshsh correct. We will very strongly depend on Next.js tracing moving forward - no escapages, except for situations where we find that Next.js spans are completely inaccurate. Note that pure Sentry users without any custom setups are a priority for us right now. Not because we don't care about the others, but because this stuff is surprisingly complex and we need to converge to a stable state step by step.
lforst commentedon Nov 6, 2024
This should be solved with the latest version of the SDK. Let us know if it works. (Only exception being Next.js Pages router API routes because Next.js emits completely wrong durations for those)
adam187 commentedon Mar 12, 2025
I finally had some time to upgrade Sentry again, looks like it's working now as expected now 🙇