You can already send OTel traces to Sentry. Point your OTLP exporter at Sentry’s endpoint, set environment variables, and your spans show up in the trace explorer. Our OTLP setup guide and “You Don’t Need to Pick One” walk you through that.
But those spans are islands. You get a trace waterfall in Sentry, sure. What you don’t get is the thing that makes Sentry valuable:
Click an error => see the OTel trace that caused it
Click a span => see the Sentry errors that fired inside
That connection between your OTel performance data and your Sentry error data doesn’t exist unless something on the SDK side actively wires them together.
