Today we’re excited to announce BindPlane OP – the first observability pipeline built for OpenTelemetry – is out of beta and now generally available. You can download the latest version here.
Two months ago we released BindPlane OP in beta, and while we were confident we had something special, the response surpassed all of our expectations.
We’ve had amazing conversations with many of you as you’ve started experimenting with the beta, already providing us with invaluable feedback. In fact you’ve even started submitting PRs and educating others on the power of BindPlane OP.
We also started a Slack community where we hope to curate a community that has the shared vision of using and building open source observability. Thank you for joining us in this endeavor. It’s been great to see so much early participation and excitement for what we’re doing.
What’s new in GA?
Quite a bit! Certainly take a look at the full changelog, but here are the highlights:
Enhanced Flow Control
Perhaps the most critical piece of an observability pipeline is having the ability to augment your telemetry. Filtering, sampling, and enriching your data should all be at your fingertips.
With this release, we’re introducing support for both metric toggling and OpenTelemetry processors, unlocking full control of your telemetry data.
Metric toggles give you the power to enable and disable the individual metrics being sent to your observability platform, increasing the signal in your data and providing an additional lever for controlling costs.
Processors are inserted between a source and destination and make it possible to manage the flow of your data.
We’re starting with 9 processors covering a wide range of use cases; these fall into a few categories:
- Filter Processor – When drilling down into an issue in your environment, refining and sculpting the data in your pipeline is critical. With the Filter processor, you can include or exclude metrics, logs, and traces based on a keyword or regular expression – keeping the data that matters most.
- Log Enrichment Processor – Do you need to enrich your logs with additional metadata? These processors let you define new key/value pairs to insert, update, upsert, or delete from your logs
- Log Sampling Processor – The thing about logs is that there are a lot of them, and you rarely need them all. This processor let’s you set a sample rate so you can get the monitoring you need while reducing costs
- Raw Processor – Is there an OpenTelemetry processor you want to use but we haven’t built into the UI yet? This will let you add the processor YAML right into your config
New Sources & Destinations
We’ve significantly expanded the number of integrations. We now have over 50 total sources, up from the 20 that were available at beta. This includes support for many that have been heavily requested, such as:
- VMware vCenter and ESXI
- Apache Wildfly
- SQL Server
- Microsoft IIS
- Apache HTTP
One of our guiding principles with BindPlane OP is to make it simple for you to “Instrument once. Send anywhere.” Supporting as many destinations as possible is what will make that reality. With GA we now support the following 10 destinations:
- Google Cloud
- Jaeger NEW
- New Relic
- OpenTelemetry (OTLP)
Agent update, one of the most critical aspects of agent management, is now available in BindPlane OP. Beginning with version 1.6 of observIQ’s distribution of the OpenTelemetry Collector you can bulk update your agents with just a single click.
This release of BindPlane OP is a crucial milestone as we work toward building open source and vendor neutral products for the collection, processing, and transport of telemetry data.
We’d love for you to help us shape the future of open source telemetry by: