Log and Trace Drains
Learn how to set up drains and forwarders to send logs and traces to Sentry.
Drains and forwarders let you send logs and traces to Sentry without modifying your application code. They're ideal when:
- You want to capture platform-level telemetry from your hosting infrastructure (e.g., Vercel Build Logs, Cloudflare Workers Traces).
- You can't install Sentry SDKs directly in your application (e.g., Nginx Traces, Postgres Logs)
- You're using an existing OpenTelemetry pipeline and want to start routing logs and traces data to Sentry via Sentry's OpenTelemetry support.
Sending error events via drains or forwarders is not currently supported. To capture errors you'll need to add the Sentry SDK to your application.
Platform drains connect your hosting platform's native telemetry system directly to Sentry (e.g., Vercel, Cloudflare, Heroku)
| Platform | Logs | Traces |
|---|---|---|
| Vercel | ✅ | ✅ |
| Cloudflare Workers | ✅ | ✅ |
| Heroku | ✅ | ✅ |
| Supabase | ✅ | ❌ |
| Shopify Hydrogen | ❌ | ✅ |
Forwarders collect logs and traces from various sources and route them to Sentry.
| Forwarder | Logs | Traces |
|---|---|---|
| OpenTelemetry Collector (recommended) | ✅ | ✅ |
| Vector | ✅ | ❌ |
| Fluent Bit | ✅ | ✅ |
- Forwarding AWS CloudWatch Logs to Sentry
- Forwarding Logs and Traces from Kafka to Sentry
- Forwarding Nginx Logs to Sentry
- Forwarding Syslog Messages to Sentry
- Forwarding Windows Event Logs to Sentry
- Logs: View, search, and analyze logs in Sentry
- Trace Explorer: View, search, and analyze traces in Sentry
- OpenTelemetry Protocol: Learn about Sentry's OpenTelemetry support and how to export OTLP data to Sentry
Sending metrics via drains or forwarders is not currently supported. If you're interested this support for this please reach out on GitHub or or email us at feedback-metrics@sentry.io.
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").