# Integrations

Integrations are the building blocks of your Bindplane telemetry pipeline. They define how telemetry data (logs, metrics, traces) is collected, processed, and exported to your preferred destinations.

## Integration Types

### [Sources](https://docs.bindplane.com/integrations/sources)

**Data Collection**: Sources define where your telemetry data originates. They connect to your infrastructure components, applications, and cloud services to ingest data into your pipeline.

**Popular Sources:**

* **OpenTelemetry (OTLP)**: Standard protocol for telemetry data
* **Kubernetes**: Events, metrics, and logs from your K8s clusters
* **AWS Services**: CloudWatch, S3, EC2, and other AWS resources
* **System Logs**: Journald, Syslog, and file-based logging
* **Application Logs**: Custom application telemetry and structured logs
* **Database Monitoring**: MySQL, PostgreSQL, and other database systems

### [Processors](https://docs.bindplane.com/integrations/processors)

**Data Processing**: Processors modify, filter, and transform your telemetry data before it reaches its destination. They help optimize data flow, reduce costs, and ensure compliance.

**Common Processors:**

* **Filtering**: Remove unwanted logs, metrics, or traces
* **Transformation**: Rename fields, modify values, or restructure data
* **Aggregation**: Combine metrics or batch logs for efficiency
* **Enrichment**: Add metadata, labels, or contextual information
* **Sampling**: Reduce data volume while maintaining observability
* **Routing**: Direct data to different destinations based on criteria

### [Connectors](https://docs.bindplane.com/integrations/connectors)

**Pipeline Bridging**: Connectors connect telemetry pipelines. They can convert telemetry between signals, generate metrics from other signals (like traces), or route telemetry to multiple downstream pipelines. Unlike processors, connectors aren’t limited to a single pipeline’s signal type.

**Common Connectors:**

* [Count](https://docs.bindplane.com/integrations/connectors/count): Emit volume counters as metrics for logs, metrics, or traces
* [Routing](https://docs.bindplane.com/integrations/connectors/routing): Route telemetry to different downstream pipelines using OTTL conditions
* [Signal to Metrics](https://docs.bindplane.com/integrations/connectors/signal-to-metrics): Generate custom metrics from logs, metrics, or traces using OTTL
* [Span Metrics](https://docs.bindplane.com/integrations/connectors/span-metrics): Generate R.E.D metrics (calls, errors, duration) from incoming spans

### [Destinations](https://docs.bindplane.com/integrations/destinations)

**Data Export**: Destinations are the final endpoints where your processed telemetry is sent for storage, analysis, or visualization.

**Popular Destinations:**

* **Observability Platforms**: Datadog, New Relic, Splunk, Elastic
* **Cloud Services**: Google Cloud Logs, AWS CloudWatch, Azure Monitor
* **Security Platforms**: Google SecOps, CrowdStrike Falcon LogScale
* **Databases**: ClickHouse, InfluxDB, TimescaleDB
* **Message Queues**: Kafka, RabbitMQ, AWS SQS
* **Custom Endpoints**: OTLP, HTTP, gRPC endpoints

## Next Steps

* [Browse available sources](https://docs.bindplane.com/integrations/sources) to see what data you can collect
* [Explore processors](https://docs.bindplane.com/integrations/processors) to understand data transformation options
* [Explore connectors](https://docs.bindplane.com/integrations/connectors) to connect pipelines and generate metrics from other signals
* [Check destinations](https://docs.bindplane.com/integrations/destinations) to find where you can send your data
* [Learn about processors](https://docs.bindplane.com/broken-reference) for advanced data processing
* [Understand rollouts](https://docs.bindplane.com/broken-reference) for safe deployment strategies


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

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

The question should be specific, self-contained, and written in natural language.
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.