Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
After working with support case TrackingID#2412181420000893, we identified that we are not able to analyze PowerBI service performance with enough details. The current tools/info is not enough.
Typical performance analysis question is: I need to know what reports were being queried and were main contributors during a capacity usage spike in a past time window. From the capacity metrics page, we can only see what dataset was queried, but it is not enough. We need to locate to the page level, report level, ideally which visual or DAX were using CPU resources excessively during the time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The capacity metrics app is focused on capacity metrics only. Workload specific metrics like analysis services memory consumption, spark metrics or DW insights fall outside of the focus area of capacity metrics and would complicate the user experience. BYOLA is a solution that you can use for obtaining AS specific metrics and if that doesn't meet your needs please submit a new idea for a more holistic monitoring solution, this is something we're considering as part of a broader monitoring effort.