Forum Discussion
Workspace Monitoring - Many errors (Instability due to data volume?)
Hello everyone,
I've recently started using Workspace Monitoring on a UAT Workspace (not used much) and on a Production Workspace (a lot of use).
On the UAT Workspace I have no problems, it works for the Live Monitoring Dashboard as well as for the .PBIT made available by the community.
Live Monitoring Dashboard :
Community PowerBI Desktop File :
However, when I use Monitoring on the Production Workspace, I get a lot of errors, certainly due to the volume of data (which wouldn't be normal...)
Live Monitoring Dashboard :
Community PowerBI Desktop File :
Are you experiencing similar problems? Can you confirm that the problem is instability?
Thank you in advance for your help,
Have a nice day,
Vivien
Hi vivien57,
Thank you for reaching out to Microsoft Fabric Community.
To resolve the issue try following the below steps:
- Try adding filters to the data at the backend and then refresh the dataset to see if the report loads correctly. If errors persist, ensure that all credentials and connections are properly configured.
- If the report loads successfully after applying filters, the issue is likely due to the large dataset size. In that case, limit the data retrieved by applying filters. Additionally, if you are performing aggregations in the front end, consider fetching pre-aggregated data directly from the backend to improve performance
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
2 Replies
Hi vivien57,
Thank you for reaching out to Microsoft Fabric Community.
To resolve the issue try following the below steps:
- Try adding filters to the data at the backend and then refresh the dataset to see if the report loads correctly. If errors persist, ensure that all credentials and connections are properly configured.
- If the report loads successfully after applying filters, the issue is likely due to the large dataset size. In that case, limit the data retrieved by applying filters. Additionally, if you are performing aggregations in the front end, consider fetching pre-aggregated data directly from the backend to improve performance
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Hello,
Thanks for the feedback. It seems to be a problem related to the amount of data, because when I filter it, it works.
We are therefore waiting for improvements from the Microsoft team 🙂
Have a nice day,
Vivien
