Administrators of Power BI Report Servers can query and potentially build report server monitoring reports on top of execution log data maintained within the Report Server Database. This data, which is stored in the ExecutionLogStorage table, is exposed via Views, such as dbo.ExecutionLog3, and includes all essential attributes of report server execution history. This includes the report requested, the user requesting the report, the time, and the data size of the activity.

The names of the Report Server Database and its host server can be found via the Database page of the Report Server Configuration Manager application, as shown in the following screenshot:

In this example, any ad hoc analyses or standard monitoring reports based on execution log data will need to access the ReportServerPBI SQL Server database hosted on the ATLAS server. As described in the Report Server reference topology section, the Report Server Database is usually hosted on a separate server than the instance of the Power BI Report Server (ATLASPBIRS).

In the following screenshot from SQL Server Management Studio (SSMS), the ExecutionLog3 view of the ReportServerPBI database is queried to retrieve execution history: 

As shown in the preceding screenshot, the Format field can be used to query for specific report types, such as Power BI (such as PBIX). The list of columns available in the execution log view and their descriptions are documented at the following URL: (http://bit.ly/2nforva).

By default, log entries are stored for 60 days. However, report server admins can modify this setting via the Logging page of Server Properties, as shown in the following screenshot:

Server properties are accessible by right-clicking on the context menu of the Power BI Report Server instance in SSMS. As described in the Report Server reference topology section, the report server instance and the Report Server Database (which stores the log data) are usually on separate physical servers.