Forwarding Data to Sentry
Forward logs and traces to Sentry from various sources using the OpenTelemetry Collector, Vector, or Fluent Bit.
Forward logs and traces to Sentry from infrastructure sources using a pipeline tool like the OpenTelemetry Collector, Vector, or Fluent Bit. For multi-project routing with automatic project creation in Sentry, use the Sentry Exporter. This approach doesn't require modifying application code.
Use forwarding when:
- You need to collect logs from infrastructure (cloud services, web servers, message queues)
- You want to process or transform telemetry before sending to Sentry
- You're aggregating data from multiple sources
- You need to route data to multiple destinations
If you just want to send traces or logs from your application code without an intermediary, see Direct Export instead.
How is this different from Log and Trace Drains? Log and Trace Drains are for managed hosting platforms (Vercel, Cloudflare, Heroku) where the platform provides and runs the telemetry pipeline for you. OTLP Forwarding is for when you run and manage the pipeline yourself (like the OpenTelemetry Collector).
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").