Anyone who uses Power BI and audits its logs will only be able to audit until dashboard level. The idea is to increase the level of detail to page level so that you can know which pages are beeing visited the most/least and by which users. This new information will enable you to modify your dashborads accordingly, enhance them and much more.
18 Comments
- This would be amazing to give more insight into how people use reports and how to make them more efficient and friendly for the end user.
- Also at dataset level please. Ideally also at workspace level with drill through into all the above details.
- You can do this already if you edit/redesign the usage dashboard that comes 'out of the box' you can see who viewed which report page, and when.
michamMicrosoft Employee
'Audit log includes info on visuals clicked in Dashboard. We need Audit log to include information on: - Page report clicked, -visual in report clicked- Office 365 users can see who visits Reports, but not their pages via Office 365 Cloud App Security.
- This would add the capability to review performance metrics of each report page . For a power BI editor, this information is very useful, and will also help to get the best out of the spend consumptions $ in Azure
- We also require this!
- Access to the underlying model is needed also. The calendar needs to be tied to each fact table. We also need the ability for an Admin or a role with access to multiple workspaces to be able to combine the activity across them.
- I need to report usage over time, by user and page, and build these data into my ongoing reporting. I need data at the page level detail that I can match up to my users and know who is using reports, how much, at a detail level so i can tie in my key event dates.
- Page level detail is important to our user metrics as well.
