The On-premises data gateway desktop application makes it easy for gateway administrators to analyze gateway request activity. As shown in the following image, the Diagnostics tab allows admins to record additional details in the gateway log files and to export these files for analysis:
Applying the additional logging setting requires the gateway to be restarted but provides visibility to the specific queries requested and the duration of their execution. In a typical troubleshooting or analysis scenario, a gateway admin would temporarily enable additional logging, execute a data refresh or query from the Power BI service, and then export the gateway log files to analyze this activity. Once the log files have been exported, additional logging should be disabled to avoid reduced query throughput.
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll
Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.dll
As an alternative to the gateway application setting, both configuration files can be accessed and modified at the installation location of the gateway, such as C:Program FilesOn-premises data gateway.
In the following example, a gateway log file with verbose logging has been copied into Excel and filtered for a specific request ID:
In the preceding example, a refresh process caused the SELECT * FROM BI.vDim_Account query to be executed against an on-premises source via the gateway. The duration of this query was 2.48 seconds (2,484 ms) per the final row containing the FireActivityCompletedSuccessfullyEvent log event. Note that column headers are not included in the log files and that the second column of the logs (a GUID) is the Request ID. This is the column that can be used to match a query with its completion event and duration.