Collector components: Connectors 🔗
The Splunk Distribution of the OpenTelemetry Collector includes and supports the connectors listed on this doc. To see other components, refer to Collector components.
Note
The following list might not contain all the latest additions. For a complete list of Collector components, including components that aren’t included in the Splunk Distribution of OpenTelemetry Collector, see the opentelemetry-contrib repository in GitHub.
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 following connectors are available:
Name |
Description |
Pipeline types |
|---|---|---|
Routing connector ( |
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 ( |
Aggregates Request, Error and Duration (R.E.D) OpenTelemetry metrics from span data. |
Traces, metrics |
Sum connector ( |
Sums attribute values from spans, span events, metrics, data points, and log records. |
Traces, metrics, logs |