Log and Trace Drains
Learn how to set up log and trace drains to send logs and traces to Sentry from managed hosting platforms.
Log and trace drains connect your hosting platform's native telemetry system directly to Sentry, letting you send logs and traces without modifying your application code.
How is this different from OTLP Forwarding? Log and trace drains use your hosting platform's built-in telemetry export feature—you just configure a destination and the platform handles the rest. OTLP Forwarding is for when you need to run your own pipeline (like the OpenTelemetry Collector) to collect data from infrastructure sources.
| Platform | Logs | Traces |
|---|---|---|
| Vercel | ✅ | ✅ |
| Cloudflare Workers | ✅ | ✅ |
| Heroku | ✅ | ✅ |
| OpenRouter | ❌ | ✅ |
| Supabase | ✅ | ❌ |
| Shopify Hydrogen | ❌ | ✅ |
Log and trace drains support logs and traces only:
- Errors: To capture errors, add the Sentry SDK to your application.
- Metrics: Not currently supported. If you're interested in this, reach out on GitHub or email feedback-metrics@sentry.io.
- OpenTelemetry Protocol (OTLP): Send OTLP data to Sentry via SDK, OpenTelemetry Collector, Vector, or Fluent Bit
- Logs: View, search, and analyze logs in Sentry
- Trace Explorer: View, search, and analyze traces in Sentry
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").