Get Gen2 Premium Capacity Users causing CPU overload through dataset activity?

[equerystrian]

I'm spending more time with the Capacity Metrics Analysis report to monitor our Gen 2 P1 Premium Capacity. It's great to see the capacity get used, but we're seeing Interactive CPU spikes and can't always trace it back to our BI team activities. Instead, we might have end users trying to use a shared dataset for something that it wasn't intended to do, or we have a performance issue to track down for a given use case. 

How do we get the actual user information behind the "IdentityClaimsHash" (what the User column actually ties to) in the Timepoint Interactive Detail? Power BI user doesn't tell me who I need to follow up with to find out whether they're trying to boil the ocean or use a Power BI dataset as an export agent. Also is there somewhere we can translate the XMLA Read Operation? I *think* that means Excel activity as we don't have end users connecting to the API's in our org.

I suppose I'm spoiled by the data we could get from Ye Olde SSRS ExecutionLog3 view so if there's a way to get similar I'd really appreciate it!

Power BI Capacity CPU spike details

[equerystrian · Accepted solution]

Per this tweet response from Benni De Jagere, "Data isn't being exposed in the underlying dataset for the Metrics App. BYOLA (Log Analytics) does allow you to get the user name. But I don't advise setting that up for all your workspaces. Manageability, cost, .. aren't "great" for a larger number of workspaces"

Next steps for me are reviewing these articles.

https://docs.microsoft.com/en-us/power-bi/transform-model/log-analytics/desktop-log-analytics-overvi... 

https://docs.microsoft.com/en-us/power-bi/transform-model/log-analytics/desktop-log-analytics-config... 

Data isn't being exposed in the underlying dataset for the Metrics App. BYOLA (Log Analytics) does allow you to get the user name. But I don't advise setting that up for all your workspaces. Manageability, cost, .. aren't "great" for a larger number of workspaces

— Benni De Jagere (@BenniDeJagere) April 19, 2022