New Features

• Additional TLS options for Postgres
• An option to change the default gRPC max incoming message size on the OTLP and Bindplane Gateway sources
• Storing attributes specified on OpAMP AgentDescription
• Additional processor recommendations for parsing sev, severity field
• Better visibility of deleted telemetry fields in Live Preview

Fixes

• Delete fields properly deletes nested fields

New Features

• New AWS S3 Rehydration Source
• New Filter By Condition Processor
• Additional MYSQL Source Metrics
• Add date picker to Azure Blob Rehydration source

AWS S3 Rehydration Source

v1.55.0 adds a new source for rehydrating data stored in an AWS S3 bucket. Read the source documentation here.

Filter By Condition Processor

Filter By Condition is a new processor introduced in v1.55.0. It can be used to include or exclude telemetry based on a condition that is evaluated against the telemetry data. Read the processor documentation here.

New Features

• New nop destination
• Processor Recommendations
• Secret key management

Processor Recommendations

v1.54.0 introduces processor recommendations. BindPlane will recommend processors when viewing Live Preview.

The initial release recommendation feature set includes the following recommendations:

• Parse Log Body as JSON
• Parse Severity
• Remove Debug Logs
• Remove Empty Values

Secret Key Management

New CLI command for rotating secret keys. Run bindplane secret --help for details.

1Manage secret keys
2
3Usage:
4  bindplane secret [command]
5
6Available Commands:
7  add         Add secret key
8  default     Set default secret key
9  delete      Delete secret key
10  get         Get secret keys

New Features

• New Telemetry Selector for components that support multiple telemetry types
• Chronicle destinations are now supported when using a Google license

Fixes

• Improved agent heartbeat
  • Resolves an issue where agents could become disconnected when using a Kubernetes Service mesh such as Istio

New Features

• New processor Condition Builder
  • Easily create OTTL conditions for most processors
  • See Upgrade and Downgrade for upgrade considerations
• New Gateway source and destination
• Add force_flush_period and max_log_size parameters to file log source

Upgrade and Downgrade

Downgrades from 1.52.0 to previous versions of BindPlane are not supported if you make use of the new OTTL condition builder feature. BindPlane 1.52.0 introduces a new parameter type that will not render

Condition Builder

The new condition builder allows the user to easily create OTTL.

Bug Fixes

• Minor UI fixes

New Features

• New Resource Detection processor. The previous processor is deprecated, with this new one matching OTel capabilities.
  • New Detectors:
    • Consul
    • AWS EKS
    • Kubernetes
    • OpenShift
  • Adds support for user-provided list of detectors
• Synthetic Telemetry Generator Source Type

Bug Fixes

• Various fixes for large-scale environments (100k agents)
• Fix for connected agents sometimes appearing as disconnected in the UI

Other

• Improvements to resource display in Configuration topology

New Features

• Agent labeling
• New Logstash source

Labels

We added new functionality that allows users to assign custom labels to agents. Agent labels can be managed either individually or in bulk. To manage labels individually, users can click on the labels in the details of the agent. To manage labels in bulk, users can select multiple agents from the agents table and click the new “Manage Labels” button that will appear. In addition to this, labels are now displayed in the agents table. If labels are truncated in this view, users can use the hover interaction to display all labels.

Bug Fixes

• VMware vCenter: Resolved an issue where disabling TLS verification would not work
• Move Fields Processor: Fixed OTTL exists condition

New Features

• Splunk HEC source support for Kubernetes Gateway
• Parse XML processor
• Initial support for OpenTelemetry Contrib collector
  • See Connecting Other OpenTelemetry Collectors Using the OpAMP Extension

Bug Fixes

• Corrupted concurrent downloads of offline agent updates
• Prevent scroll jitter in snapshot console

New Features

• Resource Library adds the ability to unlink Sources and Processors
• Application onboarding
• Determining Agent capabilities from OpAMP

New Features

• New Resource Library page for reusable Sources, Destinations, and Processors.
• New Destination: Azure Monitor
• New Destination: Snowflake
• New Processor: Parse CSV
• New Processor: Key Value processor
• Add endpoint parameter to Honeycomb Destination.

Upgrade Notes

As of 1.46.0, Prometheus is required to store agent throughput measurements. Throughput measurement support has been removed from Bolt Store and PostgreSQL.

Single-instance users do not need to take action. BindPlane will spawn a Prometheus sub-process automatically.

High-availability users will need to make sure Prometheus is configured in their environment. Documentation for configuring Prometheus in a BindPlane HA architecture can be found here.

Helm users should upgrade to chart version 1.2.0. Consult the chart release notes before upgrading. Once upgraded to Chart version 1.2.0, it is safe to upgrade to Chart version 1.2.1, which contains BindPlane v1.46.0.

New Features

• Added Splunk TCP source to Kubernetes Gateway Agent
• Added Encoding param to Kafka destination
• Added Optional Path Prefix parameter to OTLP HTTP
• New Lookup Table processor
• Agent health monitoring
• Terraform Provider: Added support for Extensions

Bug Fixes

• Added missing TLS options to CLI

New Features

• New Dynatrace Destination

New Features

• Introduced search capability to processor live preview and agent recent telemetry
• Added support for metrics to Azure Event Hub Source
• Added TLS server name override option to OTLP destination

Bug Fixes

• Removed compression option from Splunk Cloud destination
  • Compression is always enabled

Bug Fixes

Fixes an issue where changing the system account username would cause the user to lose access to their account.

It is recommended that all users upgrade from 1.43.0 to 1.43.1.

New Features

• Introduced the ability to delete old summary rollups to improve system performance and data management.

Bug Fixes

• Fix an issue where unavailable processors were shown as available for Google Edition

Other

• BindPlane OP Server architecture docs
• BindPlane OP HA Prometheus Linux Packages docs

New Features

• Azure Event Hub Source

Bug Fixes and Improvements

• Improved OpAMP debugging

Migration Notes

This release includes a change that will break future downgrade compatibility for users with a single account boltstore installation of BindPlane. Before upgrading, those users should create a backup of their storage file, which can be used in the event of a downgrade.*

To downgrade, those users should follow these steps:

1. Stop the BindPlane service
2. Replace the storage file with the backed-up version
3. Restart the BindPlane service

Changes made after upgrading will not be persisted when performing this downgrade.

* If, instead, BindPlane is configured with either multi-account or postgres, this release is backward compatible and no action is needed to downgrade safely. BindPlane is multi-account if accounts.enable is true in its configuration:

1accounts:
2  enable: true

New Features

• New destinations
  • Observe, Inc
  • Chronicle Forwarder
• Source changes
  • TCP Logs: Added new encoding option

Bug Fixes and Improvements

• Resolved an issue where Prometheus backed agent measurements were inconsistent in some cases
  • See the Upgrade Procedure notes for upgrade information

Upgrade Procedure

Prometheus

Agent measurement values will be inconsistent in some situations. Upgrading to v1.41.0 solves this issue.

If you are using BindPlane's built in Prometheus service, no action is required. If you are unsure, generally this means your BindPlane server is managing it's own Prometheus service behind the scenes. You can skip this procedure.

If you are using a self managed Prometheus instance for your measurements backend, you must update your Prometheus recording rule at /etc/prometheus/rules.yml.

1groups:
2- name: configuration-rollups
3  interval: 1m
4  rules:
5  - record: bindplane_agent_measurements:rollup:rate:1m
6    expr: sum without (agent) (rate(bindplane_agent_measurements{}[1m9s999ms] offset 10s))

Once updated, restart the service.

1sudo systemctl restart prometheus

New Features

• UI will link out to resource (source, destination, processor, extension) documentation when viewing a given resource.
• Add Compression Param to Chronicle
• Support headers for http protocol on OTLP exporters
• Extension: Go Performance Profiler (pprof)
• Extension: Health Check

Bug Fixes and Improvements

• Improved live preview loading times

New Features

• Summary Page Beta
• Updated Configuration Editing flow
• Kubernetes Gateway agent installation as deployment
• File Source sort by mtime option.
• Extension Audit Events
• Automatic removal of unused deprecated resources
• Improved error messages for CLI

New Features

• Amazon Managed Prometheus destination
• Honeycomb destination
• Rename metric processor
• Add sort by mtime option to file source
• Extensions UI
• Added TTL parameter to ClickHouse destination
• Include support bundle script in releases
  • See /var/lib/bindplane/scripts/create-support-bundle.sh after upgrading

New Features

• ClickHouse Destination Type
• Jaeger OTLP Destination Type
• Sumo Logic Destination Type
• HTTPCheck Source Type
• Extension Support
• Optional Prometheus measurements database, promising much faster and more reliable measurements

Bug Fixes

• Ongoing UI polish
• Severity processor now handles numeric values
• Deleting configuration doesn’t leave zombie agents
• Named source measurement fixes
• Unmasking sensitive parameters in sources