Forum Discussion
Premium GEN2 | Overloading & Diagnosing Problems
Hi Anonymous
This can certainly happen if people are looking to export large amounts of data because this is not how PBI is meant to be used. Yes it can be done but it should not be always done.
The good news is that you can now enable log analytics and you can get all the details of long running queries (which means big exports) which you can find out which person is running the query and what query they are running.
Using Azure Log Analytics in Power BI (Preview) - Power BI | Microsoft Docs
Super UserHi Anonymous
This can certainly happen if people are looking to export large amounts of data because this is not how PBI is meant to be used. Yes it can be done but it should not be always done.
The good news is that you can now enable log analytics and you can get all the details of long running queries (which means big exports) which you can find out which person is running the query and what query they are running.
Using Azure Log Analytics in Power BI (Preview) - Power BI | Microsoft Docs
Thanks GilbertQ - I'll investigate whether we can enable this for some of the likely culprits. Any ideas on what to be on the lookout for in the log analytics data? We've used the M365 audit log data previously to identify the number of - for example - export operations being performed, but that doesn't differentiate between a small export of a few rows or exporting an entire dataset.
Presumably log analytics gives a little more detail?
- GilbertQ
Yeah the log analytics will tell you how long the query took to run, which could give an indication of larger exports. It will also give you the DAX query, so you will be able to see what they are doing too!