> 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/may-2024/2024-05-01-release.md). # 2024-05-01-Release Version 1.55.0 • MAY 01, 2024 ## New Features * [New AWS S3 Rehydration Source](https://github.com/observIQ/bindplane-docs/blob/main/integrations/sources/aws-s3-rehydration/README.md) * [New Filter By Condition Processor](https://github.com/observIQ/bindplane-docs/blob/main/integrations/processors/filter-by-condition.md) * 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](https://github.com/observIQ/bindplane-docs/blob/main/integrations/sources/aws-s3-rehydration/README.md). ### 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](https://github.com/observIQ/bindplane-docs/blob/main/integrations/processors/filter-by-condition.md). --- # 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/may-2024/2024-05-01-release.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.