> 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/october-2025/readme-2.md). # Oct 28, 2025 - v1.96.0 Self-hosted Deprecations * Bindplane BBolt store has been deprecated since February 2025 and will be removed in January 2026. Please migrate to Postgres as soon as possible. Reach out to support if assistance is required. Features: * New Oodle destination * New macOS Unified Logging source * Updated OTLP and Bindplane Gateway sources to expose bundled batch processor options * Supports disabling bundled batch processor * Updated Fluent Forward source to support Kubernetes and OpenShift Gateway * Updated Kafka Stream source to support Kubernetes and OpenShift Gateway Bug Fixes * Allow errored agents to be upgraded * Fix an issue with Kafka Cluster source, where TLS insecure option was incorrectly set * Fix an issue where `/v1/apply` REST endpoint would return a 202 when the input was malformed. Invalid requests will now return a status 400 * Processor recommendations will no longer appear for read only users Miscellaneous * Bindplane metrics * New NATS Event Bus Server metrics * `nats.server.connection.count`: Total number of connections made to a Bindplane NATS server. * `nats.server.connections`: Current number of connections to the Bindplane NATS server. * `nats.server.data`: Number of bytes sent and received by the NATS server. * `nats.connection.rtt`: Round-trip time of the NATS server connections. * `nats.connection.pending`: Data pending to be sent by the NATS connection. * `nats.connection.uptime`: Uptime of the NATS connection * Agent IP address is now extracted from HTTP headers to better detect the agent's IP address * Removed the deprecated `forwarder` parameter from the [Google SecOps Destination](https://docs.bindplane.com/integrations/destinations/google-secops-chronicle) --- # 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/october-2025/readme-2.md?ask=&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.