> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/integrations/connectors.md).

# Connectors

## What are Connectors?

Connectors are specialized components that connect telemetry pipelines, transforming data between signal types or routing telemetry into different downstream pipelines. 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.

## Connector Categories

### Signal transformation

Convert telemetry from one signal type to another.

* Example: logs → metrics, traces → metrics.

### Routing & splitting

Split telemetry into different downstream pipelines based on conditions. This is useful when different downstream pipelines have different processing or destinations.

### Aggregation & counting

Aggregate or count telemetry events to produce new metrics.

## Available Connectors

| Connector                                                          | Input                 | Output        | Description                                                                                 |
| ------------------------------------------------------------------ | --------------------- | ------------- | ------------------------------------------------------------------------------------------- |
| [Count](/integrations/connectors/count.md)                         | Logs, Metrics, Traces | Metrics       | Count telemetry items and emit totals as metrics                                            |
| [Routing](/integrations/connectors/routing.md)                     | Logs, Metrics, Traces | Same as input | Route telemetry to downstream pipelines using OTTL conditions                               |
| [Signal to Metrics](/integrations/connectors/signal-to-metrics.md) | Logs, Metrics, Traces | Metrics       | Generate custom metrics from any telemetry type using OTTL expressions                      |
| [Span Metrics](/integrations/connectors/span-metrics.md)           | Traces                | Metrics       | Generate R.E.D metrics (calls, errors, duration) from spans. Supports exemplars and events. |

## When to Use Connectors

Use a connector when you need to:

* Generate R.E.D metrics from spans (calls, errors, duration) with [Span Metrics](/integrations/connectors/span-metrics.md)
* Count telemetry volume as metrics with [Count](/integrations/connectors/count.md)
* Create custom metrics from any telemetry data with [Signal to Metrics](/integrations/connectors/signal-to-metrics.md)
* Route telemetry to different downstream pipelines with [Routing](/integrations/connectors/routing.md)

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

## Getting Started

1. Navigate to a V2 configuration.
2. Connect a source to a destination.
3. Click the edge between the source and destination.
4. Add a connector.

{% hint style="info" %}
Connectors connect **pipelines**. Processors operate **inside** a pipeline.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bindplane.com/integrations/connectors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.