> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/release-notes/archive/2.5.0.md). # 2.5.0 Release date: May 20th, 2025 #### 1. Overview The 2.5.0 Release of Datalogz focuses on advancing the **actionability of alerts** and improving Monitor Summary Page layout. This release also includes foundational improvements in testing, observability which will further be enhanced in the upcoming versions. *** #### 2. New and Updated Features • Introduced monitor actions for Power BI (e.g., delete, export, update refresh schedule, take ownership) with corresponding scripts and UI support. • Added new monitor for detecting duplicate Power BI dataset measures. • Enhanced alert management with bulk workflow updates, sorting, and consolidated alert statistics by status. • Updated monitor classifications and action associations for Power BI, Qlik, and Tableau to improve governance, performance, and security coverage. • Refined alert filtering, sorting, and statistics, including exclusion of resolved/done alerts from counts. *** #### 3. Monitors **Monitors Summary Page Enhancement**: * Isolation of Trend Chart and Stats * Improved UX **Monitor Engine Upgrades** #### 4. Alert - Stats, Bulk Edit and Actions * Alert Stats on Alerts Page for better understanding about the current state of the Environment’s actionability. * Bulk Edit functionality to update Alert status, Priority and Assignment in Bulk at once. * Actions: Action has been provided for PBI Assets as a part of Release 2.5. We will continue to build on top of this. *** #### 4. Fixed Issues and Bugs * Monitor Engine Revamp fixes due to issues introduced in version 2.4.0 * Fixes for : Alert Table Sorting & Filters not working correctly *** #### 5. Known Bugs and Limitations * Admins shouldn’t see the teams which they are not a part of, in the Teams Dropdown. Since they are admins, they should have an option to request to be a part of the team to Owner. \[We can cover this in the upcoming releases - Carrying forward from 2.4] * All root users and the user who is creating the team should be a part of the team by default. \[Carrying forward from 2.4] *** #### 6. Breaking Changes * There are no breaking changes in this release --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.datalogz.io/guides/release-notes/archive/2.5.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.