> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/changelog/august-2024/2024-08-21-release.md).

# 2024-08-21-Release

Version 1.69.0 • AUG 21, 2024

## Bug Fixes

* Resolved an issue with Bolt Store where agent status was reported incorrectly
* Improve agents table measurements sort performance
* Resolved an issue where mutual TLS would not use the configured certificate for verifying client certificates

### Deprecations

Kafka Event Bus for BindPlane [High Availability](https://github.com/observIQ/bindplane-docs/blob/main/production-checklist/bindplane/high-availability/README.md) is deprecated, use the [built in distributed eventbus](https://github.com/observIQ/bindplane-docs/blob/main/configuration/bindplane/nats-as-event-bus.md). It is simpler to use and does not require additional infrastructure.

{% hint style="info" %}
**NOTE**

Kafka sources and destinations are unrelated and fully supported.
{% endhint %}

### Miscellaneous

* Systemd: Increase default max open files from 55,000 to 65,000


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bindplane.com/changelog/august-2024/2024-08-21-release.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.