BindPlane OP

How to Reduce Data Costs with OpenTelemetry and BindPlane OP

Paul Stefanski
Paul Stefanski

Data costs fill a large column in many organizations’ accounting sheets. Data pipeline setup and management is a large time sink for DevOps, IT, and SRE. Setting up telemetry pipelines to reduce unwanted data often takes even more time that could better be spent creating value rather than reducing costs. This blog will show you one way to quickly set up your data pipeline to filter unnecessary telemetry data.

Getting Started with OpenTelemetry and BindPlane OP

BindPlane OP is an open source tool for managing telemetry data pipelines. If you’re already using the observIQ distribution of OpenTelemetry, but haven’t used BindPlane OP to manage your agents and sources, follow this 2-minute guide on how to connect existing OpenTelemetry deployments to BindPlane OP. If you’re starting from scratch, visit the BindPlane OP GitHub page or the BindPlane OP Documentation for easy setup instructions (~3 minute setup from start to shipping telemetry).

BindPlane OP works on MacOS, Windows, and Linux. It’s vendor-agnostic, so you can use any integrated source and destination. Here you can find an updated list of supported sources and destinations. New integrations are added frequently, so check with us in the BindPlane OP Slack if you don’t see what you’re looking for. BindPlane OP is also the first telemetry pipeline built to work natively with OpenTelemetry.

Using Snapshot to Sample Data

You can sample logs directly from BindPlane OP without needing an analysis tool. Sampling logs with Snapshot is a good way to scan a source for unwanted or noisy data generation. The steps for using Snapshot are simple:

  1. Go to the Agents tab and click on the agent you want to Snapshot

2. Click “View Recent Telemetry” in the bottom left of the agent details

  • Note: if the button is grayed out, make sure your agent is updated (an update button will appear next to the “VERSION” row in Details, and that the agent is running a configuration from your CONFIGS tab. You can click “Edit” in the top right to add a config template from the CONFIGS tab.

3. Snapshot will appear and display the last 100 log messages, the most recent batch of metrics, and traces.

  • You can hit the refresh button on the top right to update the Snapshot
  • If you want to expand a log message, click on the carrot on the left.

4. Select a log you would like to reduce or exclude. You can exclude or limit the volume of logs based on any field in the log message.

With Snapshot, you can quickly identify log messages and metrics you want to reduce or filter. Once you’ve identified the necessary, redundant, or noisy data, copy the details onto a notepad or take a screenshot to inform your processor configuration.

Using Processors to Filter Telemetry Data and Reduce Costs

Processors enable OpenTelemetry agents to filter data and reduce data flow, which can dramatically reduce ingestion and analysis costs. The following steps will show how to add a processor to filter telemetry with the information collected from Snapshot.

  1. On the agent page that you want to add the processor to, click the Configuration name on the right. That will take you directly to the edit page for that configuration.

2. On the configuration page, click the source you want to add processors to

3. In the pop-up, click “Add processor” at the bottom

4. You will see many different processor types that can be added. Processors are useful for enriching data, as well as reducing it. Now, we’re focused on filtering logs to reduce costs, so we’ll use the “Log Record Attribute Filter” processor.

5. Fill in the processor details using the drop downs and copying the information from Snapshot. The “Key” is any Attribute label that appears on the left when inspecting the log. The “Value” is anything that appears to the right of the Key when inspecting the log.

  • You can add rows for as many filters as you want to run on the agent

6. Click “Save”. Your agent will update automatically and the designated logs will be filtered

You can repeat that process using the “Metric Name Filter” processor and copy the name of the metric you want to exclude. Alternatively, if you want to reduce the data flow, but not filter any data completely, use the following steps:

  1. Add a “Log Sampling” processor

2. Select the ratio of logs you want the agent to sample and click “Save”

Filtering logs and metrics and sampling logs is an excellent way to reduce data costs while still maximizing the value of your data. BindPlane OP is the first data pipeline management tool that allows you to use OpenTelemetry on all of your sources with a smooth user interface that lets you manage your entire data infrastructure in one place. To learn more about BindPlane OP, visit or come and chat with us directly in the BindPlane OP Community Slack.

Paul Stefanski
Paul Stefanski

Related posts

All posts

Get our latest content
in your inbox every week

By subscribing to our Newsletter, you agreed to our Privacy Notice

Community Engagement

Join the Community

Become a part of our thriving community, where you can connect with like-minded individuals, collaborate on projects, and grow together.

Ready to Get Started

Deploy in under 20 minutes with our one line installation script and start configuring your pipelines.

Try it now