Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.

Reply
dimitragav10_
Frequent Visitor

Power BI Fabric Audit Logs

Hello everyone!

I’m working on tracking Power BI report activity and trying to simulate the ExecutionLog3 functionality from Report Server in Fabric. To achieve this, I’m using the Power BI REST API’s Admin - Get Activity Events endpoint to monitor report activity.

However, I’ve encountered a challenge: the audit logs don’t seem to provide details on when a report started and ended, nor do they indicate the success or failure of a report execution.

What I need to track:

When a user opens a report (TimeStart) and how long it takes to respond (TimeEnd).
The status of report execution (success, failure, or internal error).
Details on ItemAction to classify different types of report activities.

Key Terms Needed in Logs:

  • ItemAction:
    1️⃣ ASModelStream
    2️⃣ ConceptualSchema
    3️⃣ DataRefresh
    4️⃣ GetExcelWorkbookInfo
    5️⃣ QueryData
    6️⃣ RenderExcelWorkbookInfo
    7️⃣ SaveToCatalog
  • Status:
    1️⃣ rsInternalError
    2️⃣ rsSuccess
  • Timestamps:
    TimeStart – When the report execution begins
    TimeEnd – When the execution completes

The API doesn’t seem to provide these timestamps or status details directly. Is there any workaround to extract this information? 

Any insights, suggestions, or best practices would be greatly appreciated!

Thanks in advance! 



1 REPLY 1
v-karpurapud
Community Support
Community Support

Hello @dimitragav10_ 

Thank you for reaching out regarding Power BI Fabric Audit Logs. We understand your need to track detailed report activity.

 

Unfortunately, the Power BI REST API’s Admin - Get Activity Events endpoint does not directly provide the start and end times of report execution and status codes like rsInternalError or rsSuccess.

 

As a workaround, you can approximate start times using the ActivityDateTime field and track status through custom logging and inferred actions.

 

To implement custom logging within your Power BI reports to capture detailed execution metrics, including start and end times and execution status, you can follow these steps:

 

Using Azure Log Analytics

 

 1. Set Up Azure Log Analytics:

  • Create a Workspace: In the Azure portal, create a Log Analytics workspace.
  • Connect Power BI: In the Power BI admin portal, configure your Premium workspace to send logs to the Log Analytics workspace.

  2. Configure Diagnostic Settings:

  • Enable Logs: In the Power BI admin portal, enable diagnostic logging for your workspace.
  • Select Log Categories: Choose categories like AuditLogs, UsageMetrics, and PerformanceMetrics.

   3. Query Logs:

  • Use KQL: In the Log Analytics workspace, use Kusto Query Language (KQL) to query and analyze logs. Extract start and end times, execution status, and other metrics.

 

If my response has resolved your query, please mark it as the Accepted Solution to assist others. Additionally, a 'Kudos' would be appreciated if you found my response helpful.

 

Thank you!

 

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

FebPBI_Carousel

Power BI Monthly Update - February 2025

Check out the February 2025 Power BI update to learn about new features.

Feb2025 NL Carousel

Fabric Community Update - February 2025

Find out what's new and trending in the Fabric community.