OpenTelemetry Protocol (OTLP)
Learn how to send OpenTelemetry traces and logs to Sentry.
This feature is currently in open beta. Please reach out to feedback-tracing@sentry.io if you have feedback or questions. Features in beta are still in-progress and may have bugs. We recognize the irony.
Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK or through a pipeline tool like the OpenTelemetry Collector. Sentry does not support OTLP metrics at this time.
If you're using a Sentry SDK alongside OTel instrumentation, you can connect them to share trace context:
| Scenario | Solution |
|---|---|
| Sentry frontend + OTel backend | Use propagateTraceparent to connect frontend traces with OTel-instrumented backend services |
| Sentry SDK + OTel in the same service | Use the OTLP Integration to share trace context between Sentry and OTel |
If you're using OTel without a Sentry SDK, or want to ingest telemetry from infrastructure sources:
- Direct Export - Configure your OTel SDK to send traces and logs directly to Sentry's OTLP endpoints
- Forwarding - Use the OpenTelemetry Collector, Vector, or Fluent Bit to forward data from infrastructure sources (CloudWatch, Kafka, Nginx, syslog, etc.)
- Log and Trace Drains - Send telemetry from managed hosting platforms (Vercel, Cloudflare, Heroku, etc.)
Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").