Integrations
Integrations represent different components in your Bindplane telemetry pipeline, including Sources, Processors, and Destinations. These integrations define how telemetry (logs, metrics, traces) is collected, processed, and exported.
Types of Integrations in Bindplane
Sources
Sources define where the telemetry originates. They are integrations with infrastructure components, applications, or cloud services that are responsible for ingesting data into your telemetry pipeline.
Examples:
- OpenTelemetry (OTLP)
- Kubernetes events, metrics, and logs
- Journald, Syslog, etc.
- AWS CloudWatch
- And more...
Processors
Processors modify or filter telemetry before it reaches the destination. They help in optimizing data flow, reducing costs, and ensuring compliance.
Examples:
- Filtering out specific logs
- Renaming fields
- Aggregating metrics
- Batching logs
- And more...
Destinations
Destinations are the final endpoints where the processed telemetry is sent for storage, analysis, or visualization.
Examples:
- Google SecOps
- Google Cloud Logs
- Datadog
- New Relic
- Elastic
- Grafana
- OTLP endpoints
- Kafka
- ClickHouse
- And more...
How Integrations Work in Bindplane?
Integrations are modular and can be mixed and matched to build flexible telemetry pipelines. All integrations in Bindplane are represented as a YAML files and can be saved, re-used, and migrated as needed.