Connectors are specialized components that connect telemetry pipelines, transforming data between signal types or routing telemetry to multiple destinations. Unlike processors that modify data within a single pipeline, connectors can change the telemetry type (for example, convert logs to metrics) or split data flows across pipelines.
Convert telemetry from one signal type to another.
Example: logs → metrics, traces → metrics.
Route the same telemetry to multiple downstream pipelines. This is useful when different downstream pipelines have different processing or destinations.
Aggregate or count telemetry events to produce new metrics.
Logs, Metrics, Traces
Metrics
Generate custom metrics from any telemetry type using OTTL expressions
Traces
Metrics
Generate R.E.D metrics (calls, errors, duration) from spans. Supports exemplars and events.
Use a connector when you need to:
Generate R.E.D metrics from spans (calls, errors, duration)
Count log events as metrics for monitoring
Create custom metrics from any telemetry data
Route different telemetry to different backends
Fan-out the same telemetry to multiple downstream pipelines
Use a processor instead when you:
Want to modify data without changing its type
Need to filter, enrich, or transform within the same signal type
Navigate to a V2 configuration.
Connect a source to a destination.
Click the edge between the source and destination.
Add a connector.
Connectors connect pipelines. Processors operate inside a pipeline.
Last updated
Was this helpful?
Was this helpful?
