> 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.7.md).

# 2.7

## Improvements

#### Expanded monitors across BI platforms

* **Tableau:** Governance, Performance, and Cost monitors to track drift, load times, and spend.
* **Power BI:** New Performance monitors to pinpoint slow workspaces and reports.
* **Qlik:** Cost, Performance, and Security monitors for end-to-end oversight.

#### BI Similarity upgrades

* Improved comparison scoring for more accurate “look-alike” detection.
* Additional Power BI metadata capture to enrich similarity analysis.

#### UX improvements

* Breadcrumbs added across pages for better orientation (no redundant “Home”).
* Consistent iconography via shared components.
* Guardrails to prevent duplicate team and connector names.

#### Performance

* Home page APIs: faster load and more stable summaries.
* BI Similarity: reduced compute time and smoother navigation.
* Inventory: noticeable speed-ups on large estates.

### Bug fixes (highlights)

* Fixed rare 404 on Insights when no executive teams are set up.
* Corrected BI Similarity acceptance and upstream lineage edge cases.
* Fixed layout issues when cloning monitors.


---

# 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.7.md?ask=<question>&goal=<endgoal>
```

`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.