Collector Pipeline: Receivers, Processors, Exporters
What you'll learn: How to configure the OpenTelemetry Collector pipeline by connecting receivers (data inputs), processors (data transformations), and exporters (data outputs) to create a flexible telemetry routing system.
Understanding the Pipeline Flow
The OpenTelemetry Collector operates as a three-stage pipeline, much like a factory assembly line for telemetry data. Data flows through three distinct stages:
Receivers are the entry points—they ingest telemetry data from various sources (applications, other collectors, cloud services). Think of them as loading docks accepting deliveries in different formats.
Processors transform, filter, or enrich the data as it passes through. They're like quality control stations that modify packages before sending them onward—adding labels, filtering out noise, batching items together, or sampling high-volume data.
Exporters send the processed data to backend systems like Jaeger, Zipkin, Prometheus, or cloud observability platforms. These are your shipping departments, packaging data for specific destinations.
Pipeline Configuration
A typical collector configuration defines these components and links them in a pipeline:
receivers:
otlp:
protocols:
grpc:
http:
processors:
batch:
memory_limiter:
exporters:
jaeger:
endpoint: jaeger:14250
service:
pipelines:
traces:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [jaeger]
This configuration creates a trace pipeline: receive OTLP data → apply memory limits and batching → export to Jaeger.
Why This Matters
The pipeline architecture provides flexibility: you can receive data from multiple sources simultaneously, apply different transformations based on your needs, and fan out to multiple backends—all without modifying your application code.
Key Takeaway: The OpenTelemetry Collector pipeline (receivers → processors → exporters) creates a configurable data routing system that ingests telemetry from various sources, transforms it as needed, and delivers it to your observability backends.