Langfuse Traces for the Vercel AI SDK no longer being uploaded after adding Sentry

[leo-paz]

hello! I recently added sentry to my nextjs application and now I don't see any of my traces going to langfuse and if I add debug: true to the exporter, I don't see anything outputted to the console either. I have verified my keys are correct and even created new ones.

I'm sure this is something obvious but can someone help me on what else to try?

[dosubot[bot]]

I found a similar discussion that might be relevant to your issue. In a thread titled "Custom" traces not creating when Next.js Vercel instrumentation is on, a solution was suggested to add await langfuse.flushAsync() at the end of the endpoint execution. Additionally, using Next.js's waitUntil was recommended to avoid blocking the HTTP response ^[1].

Regarding your current issue, when integrating Sentry with a Next.js application, it's important to ensure that Sentry's OpenTelemetry setup does not conflict with Langfuse's tracing. If you are using Sentry, you should either set skipOpenTelemetrySetup: true in Sentry.init or follow Sentry’s documentation on manually setting up Sentry with OpenTelemetry to avoid conflicts. This ensures that both Sentry and Langfuse can coexist without interfering with each other's tracing capabilities ^[2].

Additionally, make sure that the NEXT_PUBLIC_LANGFUSE_TRACING_SAMPLE_RATE environment variable is set correctly, as it determines the percentage of transactions captured for performance monitoring. If this is not set, it defaults to 0, meaning no transactions are captured ^[3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[leo-paz]

@dosu, setting skipOpenTelemetrySetup: true fixed it but is this really advised? Would this mean that sentry stops collecting openTelemetry data?

[dosubot[bot]]

Setting skipOpenTelemetrySetup: true in Sentry is advisable when using both Sentry and Langfuse in a Next.js application to prevent tracing conflicts. However, this does not mean that Sentry will stop collecting OpenTelemetry data; it simply prevents Sentry from automatically setting up OpenTelemetry, allowing you to manually configure it to ensure compatibility with Langfuse tracing ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[marcklingen]

Can you confirm that this worked? Great to see that dosu was helpful here

[leo-paz]

@marcklingen I can confirm it started sending all my traces to langfuse but I'll have to wait and see to make sure traces are still beings sent to sentry

[marcklingen]

ok sounds good, thanks for sharing