# 2024-02-28-Release

## Upgrade Notes

{% hint style="warning" %}
**IMPORTANT**

🚧 BindPlane v1.46.0 contains breaking changes.
{% endhint %}

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](https://github.com/observIQ/bindplane-docs/blob/main/production-checklist/bindplane/single-instance.md) users do not need to take action. BindPlane will spawn a Prometheus sub-process automatically.

[High-availability](https://github.com/observIQ/bindplane-docs/blob/main/production-checklist/bindplane/high-availability/README.md) 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](https://github.com/observIQ/bindplane-docs/blob/main/production-checklist/bindplane/high-availability/prometheus/README.md).

Helm users should upgrade to chart version [1.2.0](https://github.com/observIQ/bindplane-op-helm/releases/tag/bindplane-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](https://github.com/observIQ/terraform-provider-bindplane/releases/tag/v1.1.0)

## Bug Fixes

* Added missing TLS options to CLI


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bindplane.com/changelog/february-2024/2024-02-28-release.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.