You spent months instrumenting your app with OpenTelemetry. The idea of ripping it out to adopt a new observability backend is not an option.
Sentry’s OTLP endpoint means you don’t have to. In fact, two environment variables are all you need and your existing traces start showing up in Sentry’s trace explorer.
Sentry’s OTLP support is currently in open beta. This means you can start using it today, but there are some known limitations we’ll cover later.
Why OTLP: keep your instrumentation, just change the destination
The main advantage of using OpenTelemetry is that your instrumentation stays vendor-neutral. Your instrumentation code uses OpenTelemetry’s standard APIs, and OTLP (the protocol) sends that data to any compatible backend. This means you can switch observability backends anytime by changing a few configuration lines. This is particularly useful if you:
