📢 Expanding OpenTelemetry Support: OTLP Endpoint in Sentry #85902
Dhrumil-Sentry
announced in
Problem Understanding
Replies: 1 comment 2 replies
-
This is great news! We are currently implementing a SaaS product into our environment and they support OpenTelemetry out of the box, but we would have to setup our own collector and maintain it in our own environment to be able to send spans to Sentry, so being able to have our SaaS product send spans directly would Sentry would be a life-saver! |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As part of our ongoing commitment to supporting developers using OpenTelemetry to instrument their apps, we’re excited to announce that Sentry is working on native OTLP ("OpenTelemetry Protocol") support for tracing. Soon, you'll be able to send traces directly to Sentry from your applications or via an OpenTelemetry Collector—no extra setup needed.
Why Are We Doing This?
Sentry’s SDKs already capture errors, spans, replays, profiles, and everything else you need to keep your applications running smoothly. That’s not changing. But we also know that many developers have already invested in OpenTelemetry’s tracing ecosystem, and asking them to reimplement their custom instrumentation to use Sentry is a friction point—time spent moving over is time not spent shipping code.
Some of our SDKs offer a bridge between OpenTelemetry and Sentry, but for users working with our other SDKs—or those managing a complex OpenTelemetry pipeline—the experience hasn’t been seamless. We’re fixing that.
What’s Coming?
OTLP is the standard protocol for sending telemetry data in OpenTelemetry. With Sentry’s upcoming OTLP endpoint for traces, developers who have already instrumented their apps with OpenTelemetry will have a frictionless way to send that data to Sentry—whether directly from an application or via an OpenTelemetry Collector.
What this means for you:
✅ If you’re using OpenTelemetry today, you’ll be able to send traces to Sentry with minimal effort.
✅ Everything will be stitched together inside Sentry—no extra work required.
And if OpenTelemetry isn’t on your radar yet? No problem—Sentry’s SDKs will continue to provide the same tracing and insights you use today.
What’s Next?
To ensure a smooth experience for OpenTelemetry users, we’re making some tweaks to our span model to better align with OpenTelemetry’s structure. We’ll share more details in the coming weeks as we refine the implementation.
🚀 If you're using OpenTelemetry today (or thinking about it), we’d love to hear from you! What’s working? What’s not? How can we make integrating OpenTelemetry with Sentry easier? Drop your thoughts below! 👇
Beta Was this translation helpful? Give feedback.
All reactions