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

# 2.2.0

**Release date:** December 2, 2024

### Overview

This release emphasizes **connector improvements** and **Power BI refactoring**, targeting enhanced functionality and performance, particularly for PBI. These platform enhancements align with our strategic goals to improve connector management, boost user engagement through superior UX, fortify system security, and ensure scalable technical performance.

### New and Updated Features

* **Streamlined Connector Setup and Management:**
  * Connecotrs now have more detailed informationabout credentials, connection status, and authentication methods used for each data source. This provides better visibility and troubleshooting capabilities for administrators.
* **Power BI Sync Refactor**
  * Improved issue with running into rate limits when accessing Power BI connector. The new DAG implementation includes improved rate limiting and retry logic, significantly reducing API throttling issues and ensuring more reliable data collection.
* **Capacity data ingestion**
  * Power BI capacity data collection has been enhanced to include detailed metrics on capacity instances, usage patterns, and resource allocation
  * New data on capacity overages help administrators proactively manage resources and prevent performance issues.
  * Visualization of capacity metrics is now available on the insights page
* **Sudo admin (Internal)**
  * Sudo admin functionality is now fully compatible with v2 architecture
  * Enhanced UI safety features to prevent accidental resource creation in client environments
  * General UI bug fixes
    * Fixed logout functionality for sudo admins, enabling proper logout and login as regular users
  * Improved sudo admin email domain configuration
    * Added ability to manage sudo admin email domains through environment variables, extending sudo admin access beyond `@datalogz.io` domain
* **PBI Insights Page**
  * Redesigned inventory and activity plots for better visualization of Power BI workspace usage and data refresh patterns
  * Added new interactive charts showing capacity utilization trends and peak usage periods

### Metrics & Monitors

Metrics\_2.2.0

* Capacity data is now available. This include general inforation about the capacity instances and also data on overages
* link to exisiting monitors: [Datalogz Monitors](https://docs.google.com/spreadsheets/d/1_MCYMxf4WwDUZvZtCX532QouNEYu3KgrJLN5vimk480/edit?gid=1585326054#gid=1585326054)

### Fixed Issues/Bugs

Call out bugs and link/download to slack table at end or release

### Known Bugs and Limitations

The release includes two known customer-facing bugs and one internal issue:

1. **Backend Alembic Migration on Monitors (Patch 2.2.2)**: Affects customers only during upgrades.
2. **Capacity Data Extract/Copy Failure for Data Exceeding 16MB (Patch 2.2.2)**: Impacts customers using Power BI.
3. **Sudo/Admin Dropdown Not Displaying in Frontend (Patch 2.2.1)**: Internal issue with no customer impact.

### **Breaking Changes**

With this release the PBI tables have drastically changed and wilil be incompatible with prior data connectors. It’s required that old connectors be deleted and new ones created


---

# 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.2.0.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.