Collector components: Connectors

Learn about the components that make up the OpenTelemetry Collector.

A connector is both an exporter and receiver. As the name suggests a Connector connects two pipelines: it consumes data as an exporter at the end of one pipeline and emits data as a receiver at the start of another pipeline. It may consume and emit data of the same data type, or of different data types. A connector might generate and emit data to summarize the consumed data, or it might simply replicate or route data.

The Splunk Distribution of the OpenTelemetry Collector includes the connectors listed in the following table. To see other components, refer to Collector components.

Note: This table might be out of date. For a complete list of collector components, including components that aren't included in the Splunk Distribution of OpenTelemetry Collector, see opentelemetry-collector-contrib.

Name

Description

Pipeline types

Routing connector (routing)

Routes logs, metrics or traces based on resource attributes to specific pipelines using OpenTelemetry Transformation Language (OTTL) statements as routing conditions.

Traces, metrics, logs

Span Metrics connector (spanmetrics)

Aggregates Request, Error and Duration (R.E.D) OpenTelemetry metrics from span data.

Traces, metrics

Sum connector (sum)

Sums attribute values from spans, span events, metrics, data points, and log records.

Traces, metrics, logs