> 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/monitor-releases.md). # Monitor Releases ## Monitor Release December 2025 We’re excited to introduce several new Power BI monitors that help you better understand dataset behavior, reduce unnecessary costs, and ensure your users always have access to trustworthy, up-to-date data. These enhancements make it easier to spot inefficiencies and resolve issues before they impact your business. ### **Power BI Monitor: Inactive Reports with Long Refresh Durations (1–2 hours, 2–3 hours and more than 3 hours)** We’ve added three new monitors that identify reports with no user activity but long-running semantic model refreshes. **Why this matters:**\ Long refresh times on unused reports can drive up compute costs and slow down your analytics environment. These monitors help you quickly pinpoint where optimizations, reduced refresh frequency, or content retirement may be beneficial. ### **Power BI Monitor: Reports with Failed Dataset Refresh (with active users)** This monitor flags reports that have recent user activity but whose underlying semantic model failed to refresh. **Why this matters:**\ Your users may be viewing stale or incomplete data without realizing it. This monitor helps you catch refresh failures early so you can restore data quality and maintain trust in your BI reporting. It also provides analytics that reveal where failures most often occur and highlight trends, enabling faster diagnosis and more proactive issue prevention. --- # 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.datalogz.io/guides/release-notes/monitor-releases.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.