Sentry tracing breaking the tracing of my Open Telemetry instrumentation in NextJs app #19099
Unanswered
elnatantorres
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, guys! How are you?
I have instrumented a NextJs app with Open Telemetry to export traces to Grafana Tempo. I am basically using the default instrumentation provided by the package
@vercel/otelwith thePrismaInstrumentationprovided by@prisma/instrumentation. This app also uses the Sentry SDKs:@sentry/nextjse@sentry/profiling-node.When I test it without Sentry instrumentation, the trace is generated with all prisma spans. But when I test with Sentry SDK, two traces are generated and the prisma spans are attached to the trace with
instrumentationLibrary:@sentry/node. Additionally, the other trace, generated by my Open Telemetry intsrumentation, gets the attribute'sentry.drop_transaction': true.I already tried to disable Sentry tracing in many ways, but with no success:
__SENTRY_TRACING__=false,excludeTracingofbundleSizeOptimizationsinwithSentryConfigtracesSampleRateandtracesSamplerofsentry.server.config.tsto undefinedThe traces stopped being sent to Sentry, but the SDK keeps breaking my Open Telemetry traces.
Is there a way that I can use the Sentry SDK in my NextJs app and still instrument my app with Open Telemtry?
I will leave here the code that shows how my app is configured.
sentry.server.config.tssentry.edge.config.tssentry/client.config.tsconfig in next.config.jsinstrumentation.tspackage.jsonBeta Was this translation helpful? Give feedback.
All reactions