Identifying Visuals and DAX Queries Causing Spikes in CU% Using Fabric Premium Capacity App

[Anonymous]

• I'm using the new Fabric Premium Capacity App to monitor our Premium Capacity tenant. Recently, I noticed a significant spike in Capacity Units (CU%), which I've traced to interactive queries. (see screenshot below).
• From the "CU% over time" visual in the report, I could drill down to see the specific report/dataset causing the overload.
• I can see for example, a single query consumed 49% of our P2 capacity for an hour before failing (see screenshot).
• I've identified the Report/Dataset and user from the "Interactive operations for Timerange" table (see screenshot ).
• I now need to pinpoint the exact visual and DAX query responsible for this spike. This information is key for investigating and optimizing the DAX query.
• QUESTION : Is there a way to directly identify the problematic visual and DAX query from within the Fabric Premium Capacity Reporting tools? 
• I am aware the "Performance Analyser" tool inside Power BI Desktop could do this, but also requires downloading the PBIX from the service, and sequentially running the analyser on each report page. 

[Anonymous]

Hi @Anonymous ,

Please review the following documentation and check if that is what you want.

Learn about Direct Lake in Power BI and Microsoft Fabric - Power BI | Microsoft Learn

Best Regards

[Anonymous]

Hmm. Not sure what the relevance of Fabric DL is to this question (on the Capacity Metrics App).