Observability pipeline configuration¶

Observability pipeline configuration refers to the definition of data processing workflows within an observability system, typically managed through a [[Pipeline|pipeline]] structure that consists of three main stages: receivers, processors, and exporters^[open-telemetry-als.md].

Pipeline Components¶

A standard configuration uses a batch processor to handle data flow, organizing the movement of telemetry from input receivers through processing stages and finally to output exporters^[open-telemetry-als.md].

Receivers¶

Receivers define the entry point for telemetry data. In the sample configuration, an OpenTelemetry Protocol (OTLP) receiver is set up to accept data via gRPC and HTTP protocols^[open-telemetry-als.md].

Processors¶

Processors act on the data between reception and export. The configuration specifies a batch processor, which is used to group data for optimized transmission^[open-telemetry-als.md].

Exporters¶

Exporters send the processed data to a backend. The configuration uses a logging exporter that outputs to standard output (stdout) for debugging purposes^[open-telemetry-als.md].

Configuration Example¶

Below is a configuration for a logs pipeline within the otel-collector service^[open-telemetry-als.md]:

receivers:
  otlp:
    protocols:
      grpc:
      http:
processors:
  batch:
exporters:
  logging:
    loglevel: debug
service:
  pipelines:
    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [logging]

Sources¶

^[open-telemetry-als.md]