The BindPlane Distro for OpenTelemetry Collector (BDOT Collector) is observIQ’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.
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.
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.
The BDOT Collector is observIQ’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.
Increases the accessibility of OpenTelemetry by providing simplified installation scripts, tested example configurations, and end-to-end documentation making it easy to get started.
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
Tested, verified, and supported by observIQ.
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.
Install BDOT Collector using the installation script below.
sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-otel-collector/releases/latest/download/install_unix.sh)" install_unix.shTo install directly with the appropriate package manager, and how to configure OpAMP, see installing on Linux.
To install the BDOT Collector on Windows run the Powershell command below to install the MSI with no UI.
msiexec /i "https://github.com/observIQ/bindplane-otel-collector/releases/latest/download/observiq-otel-collector.msi" /quietAlternately, 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.
Install BDOT Collector using the installation script below.
sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-otel-collector/releases/latest/download/install_macos.sh)" install_macos.shFor more installation information, and how to configure OpAMP, see installing on macOS.
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 config.yaml file just like you would an OpenTelemetry Collector. To find your config.yaml file based on your operating system, reference the table below:
| OS | Default Location |
|---|---|
| Linux | /opt/observiq-otel-collector/config.yaml |
| Windows | C:\Program Files\observIQ OpenTelemetry Collector\config.yaml |
| macOS | /opt/observiq-otel-collector/config.yaml |
For more information on configuration see the Configuration section.
Improving developer experience with OpenTelemetry is observIQ'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.
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 --help argument.
For supported receivers and their documentation see receivers.
For supported processors and their documentation see processors.
For supported exporters and their documentation see exporters.
For supported extensions and their documentation see extensions.
For supported connectors and their documentation see connectors.
Here's a sample setup for hostmetrics on Google Cloud. To make sure your environment is set up with required prerequisites, see the Google Cloud Exporter Prerequisites page. Further details for this GCP example can be found here.
# Receivers collect metrics from a source. The hostmetrics receiver will get
# CPU load metrics about the machine the collector is running on every minute.
receivers:
hostmetrics:
collection_interval: 60s
scrapers:
cpu:
disk:
load:
filesystem:
memory:
network:
paging:
processes:
# Exporters send the data to a destination, in this case GCP.
exporters:
googlecloud:
# Service specifies how to construct the data pipelines using the configurations above.
service:
pipelines:
metrics:
receivers: [hostmetrics]
exporters: [googlecloud]BindPlane is designed to be OpenTelemetry-first, with OpenTelemetry as its core framework, to create a unified toolset with data ownership. By providing a centralized management plane, it simplifies the development, implementation, management, and configuration of OpenTelemetry.
To learn more about configuring OpAMP, see OpAMP Configuration, or get started with BindPlane Telemetry Pipeline below.
BindPlane Cloud is the quickest way to get started with OpenTelemetry-native telemetry pipelines. It offers managed infrastructure along with instant, free access for development projects and proofs of concept.
You can also get started with BindPlane On Prem for free by hosting it yourself.
Have an idea to improve the BindPlane Distro for OpenTelemetry Collector? Here's how you can help:
- Star this repo ⭐️ and follow us on Twitter.
- Upvote issues with 👍 so we know what to prioritize in the road map.
- Create issues when you feel something is missing or wrong.
- Join our Slack Community, and ask us any questions there.
The BindPlane Distro for OpenTelemetry Collector is an open source project. If you'd like to contribute, take a look at our contribution guidelines and developer guide.
All sorts of contributions are welcome and extremely helpful. 🙌
If you need any additional help feel free to reach out to us at support@observiq.com.