# Forwarding Pipelines

Pipelines collect telemetry from infrastructure sources (like log files, message queues, or cloud services) and forward it to Sentry via OTLP. Use a pipeline to forward infrastructure telemetry to Sentry. This works alongside or instead of SDK instrumentation in your applications.

| Pipeline                                                                                          | Best For                                                   |
| ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| [OpenTelemetry Collector](https://docs.sentry.io/concepts/otlp/forwarding/pipelines/collector.md) | Supports logs and traces from many sources                 |
| [Sentry Exporter](https://docs.sentry.io/concepts/otlp/forwarding/pipelines/sentry-exporter.md)   | Multi-project routing with automatic project creation      |
| [Vector](https://docs.sentry.io/concepts/otlp/forwarding/pipelines/vector.md)                     | Log routing with powerful filtering and low resource usage |
| [Fluent Bit](https://docs.sentry.io/concepts/otlp/forwarding/pipelines/fluentbit.md)              | Logs and traces with minimal resource footprint            |

**Not sure which to use?** Start with the [OpenTelemetry Collector](https://docs.sentry.io/concepts/otlp/forwarding/pipelines/collector.md). It supports many data sources (see our [source guides](https://docs.sentry.io/concepts/otlp/forwarding/sources.md) for common examples).

## Pages in this section

- [OpenTelemetry Collector](https://docs.sentry.io/concepts/otlp/forwarding/pipelines/collector.md)
- [Sentry Exporter](https://docs.sentry.io/concepts/otlp/forwarding/pipelines/sentry-exporter.md)
- [Vector](https://docs.sentry.io/concepts/otlp/forwarding/pipelines/vector.md)
- [Fluent Bit](https://docs.sentry.io/concepts/otlp/forwarding/pipelines/fluentbit.md)
