Description: We are currently facing challenges with monitoring our Power BI instances due to the absence of the memory consumption metric in the capacity metrics app. The current CU consumption metric does not provide a complete picture, leading to gaps in monitoring and difficulties in identifying issues with our Power BI reports.
Problem Statement: Previously, the capacity metrics app provided insights into memory consumption, which allowed us to effectively monitor and manage our Power BI instances. However, with the removal of this metric, we are now unable to fully understand the behavior of our instances based solely on CU consumption. This has resulted in a lack of comprehensive monitoring and has impacted our ability to address performance issues promptly.
Proposed Solution: We propose that Microsoft reinstates the memory consumption metric in the capacity metrics app. This would provide a more holistic view of resource utilization and enable us to monitor our Power BI instances more effectively. By having access to memory consumption data, we can better manage our resources, identify potential issues early, and ensure optimal performance of our Power BI reports.
on:
Get rid of Microsoft sidebar in Power BI new works...
on:
Improve Bookmark Pane Usability: Persistent Menus,...
on:
Case Sensitivity ragrdless of the connection type ...
frithjof_v
on:
Lakehouse SQL Analytics Endpoint snapshots
on:
Power Query - Feature addition - To keep duplicat...
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 these 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.