Forum Discussion

monicaliou's avatar
monicaliou
New Member
1 year ago
Solved

Usage Metrics Report Showing Incorrect Page Views After 08/23/2025

Hello,   I’ve noticed an issue with the Report Usage Metrics. Starting on 08/23/2025, the Page Views per day dropped to unusually low values, even though no dashboards were removed and user activit...
Need Help
  • tayloramy's avatar
    tayloramy
    1 year ago

    hi monicaliou 


    I have recieved a reply from Microsoft, and it seems the best way to fix this is to delete the usage metrics semantic model and re-create it. 

    1. Open the target workspace in the Power BI service.
    2. Navigate to Workspace Settings → System Storage → Usage Metrics Report → Delete.

      • Refer to the screenshot below for visual guidance.

         

    3. Refresh the Power BI page.
    4. Reopen the target workspace, click the three dots next to the report, and select Usage Metrics Report. A new report will be generated.

    5. Check the refresh timestamp at the bottom of the newly created Usage Metrics report. And the Usage metrics report will update automatically.


       

    Note: Deleting the Usage Metrics report will not remove any underlying data. To perform this action, you must have either Contributor or Admin access to the workspace. You can verify your access level by selecting Manage Access, located next to the workspace settings.


    If you found this helpful, cosnider giving Kudos. If I solved your problem or answered your question, mark this post as a solution. 
    Proud to be a Fabric Community member 

tayloramy's avatar
tayloramy
Icon for Super User rankSuper User
1 year ago

Hi monicaliou , 

I have noticed similar issues before where the credentials that the Usage Metric Report uses expire. 

I have not been able to find a solution yet. 

 

What happens is the credentials expire, and then the scheduled refresh for the Usage Metrics Report automatically stops. 
Normally when this happens on a semantic model, you just need to update the credentials and then do a manual refresh and the automatic refresh will kick back in, however in this case because we can't see the semantic model in the workspace, we can't do that manual refresh. 

 

I have tried refreshing from the XMLA endpoint and that also does not work. 

 

I have raised this with my Microsoft CSAM and I've had no solution as of yet. I will poke him again and see if he's gotten any answers yet. 

 

If you found this useful, consider giving Kudos. If I solved your problem, mark this post as the solution.