back to home

observIQ / bindplane-otel-collector

Bindplane’s distribution of the OpenTelemetry collector providing a simple and unified solution to collect, refine, and ship telemetry data anywhere

170 stars
44 forks
39 issues
GoShellMakefile

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing observIQ/bindplane-otel-collector in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/observIQ/bindplane-otel-collector)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

The Bindplane Distro for OpenTelemetry Collector (BDOT Collector) is Bindplane’s distribution of the upstream OpenTelemetry Collector . It’s the first distribution to implement the Open Agent Management Protocol (OpAMP) and is designed to be fully managed with Bindplane Telemetry Pipeline . The BDOT Collector is built using the OpenTelemetry Collector Builder . Get Started!  👉  Website  |  Docs  |  How-to Guides  |  Feature Guides  |  Blog  |  OTel Hub  |  Slack Learn how to connect Bindplane Distro for OpenTelemetry Collector to telemetry sources and destinations , and use processors to transform data. Why Bindplane Distro for OpenTelemetry Collector? If you're managing telemetry at scale you'll run in to these problems sooner or later: • **Agent fatigue.** You'll manage endless proprietary agents and OpenTelemetry Collectors that collect and forward telemetry to different observability backends, leading to performance issues. • **Endless configuration files.** Even with GitOps practices you'll have to manage hundreds of configuration files for different sources, destinations, and processors written in either proprietary languages or YAML. • **High complexity.** OpenTelemetry's complexity and learning curve make it difficult to implement, manage, and re-point telemetry without a centralized management plane like Bindplane Telemetry Pipeline to standardize telemetry ingestion, processing, and shipping, with a unified, OpenTelemetry-native pipeline. An OpenTelemetry Collector you're used to The BDOT Collector is Bindplane’s distribution of the upstream OpenTelemetry Collector. It’s the first distribution to implement the Open Agent Management Protocol (OpAMP) and is designed to be fully managed with Bindplane Telemetry Pipeline. Focused on usability Increases the accessibility of OpenTelemetry by providing simplified installation scripts, tested example configurations, and end-to-end documentation making it easy to get started. All the best parts of OpenTelemetry and more Bundled with all core OpenTelemetry receivers, processors, and exporters as well as additional capabilities for monitoring complex or enterprise technologies not yet available in upstream releases Always production-ready and fully-supported Tested, verified, and supported by Bindplane. Getting Started Follow the Getting Started guide for more detailed installation instructions, or view the list of Supported Operating System Versions. To continue with the quick start, follow along below. Linux Install BDOT Collector using the installation script below. To install directly with the appropriate package manager, and how to configure OpAMP, see installing on Linux. Windows To install the BDOT Collector on Windows run the Powershell command below to install the MSI with no UI. Alternately, for an interactive installation download the latest MSI. After downloading the MSI, simply double click it to open the installation wizard. Follow the instructions to configure and install the BDOT Collector. For more installation information, and how to configure OpAMP, see installing on Windows. macOS Install BDOT Collector using the installation script below. For more installation information, and how to configure OpAMP, see installing on macOS. Next Steps BDOT Collector default With the BDOT Collector installed, it will start collecting basic metrics about the host machine printing them to the log. To further configure your collector edit the file just like you would an OpenTelemetry Collector. To find your file based on your operating system, reference the table below: | OS | Default Location | | :------ | :-------------------------------------------------------------- | | Linux | | | Windows | | | macOS | | For more information on configuration see the Configuration section. Manage BDOT Collector with Bindplane Telemetry Pipeline via OpAMP Improving developer experience with OpenTelemetry is Bindplane's primary focus. We're building Bindplane Telemetry Pipeline to help deploy and manage OpenTelemetry Collectors at scale, but retain core OpenTelemetry Standards for terminology and configuration, with the added benefit of enabling remote management with OpAMP. The BDOT Collector can be configured as an OpenTelemetry Collector that is managed by the Bindplane Telemetry Pipeline via OpAMP. Bindplane is designed to be OpenTelemetry-first, with OpenTelemetry as its core framework. By providing a centralized management plane, it simplifies the development, implementation, management, and configuration of OpenTelemetry. For more information on managing collectors via OpAMP see the Connecting to Bindplane Telemetry Pipeline with OpAMP section. Configuration The BDOT Collector uses OpenTelemetry Collector configuration. For sample configs, see the config directory. For general configuration help, see the OpenTelemetry docs. For configuration options of a specific component, take a look at the README found in their respective module roots. For a list of currently supported components see Included Components. For a list of possible command line arguments to use with the BDOT Collector, run the collector with the argument. Included Components > [!NOTE] > Custom Bindplane components (receivers, processors, exporters, and extensions) have been migrated to observiq/bindplane-otel-contrib. These modules are retained for reference and will be removed after September 2026. Receivers For supported receivers and their documentation see receivers. Processors For supported processors and their documentation see processors. Exporters For supported exporters and their documentation see exporters. Extensions For supported extensions and their documentation see extensions. Connectors For supported connectors and their documentation see connectors. Example Here's a sample setup for on Google Cloud. To make sure your environment is…