> 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/january-2024/2024-01-24-release.md).

# 2024-01-24-Release

Version 1.41.0 • JAN 24, 2024

## 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](#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`.

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

Once updated, restart the service.

```bash
sudo systemctl restart prometheus
```


---

# 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/january-2024/2024-01-24-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.