Report: FUAM Gateway Monitoring - GT-Analytics/fuam-basic GitHub Wiki

Gateway Monitoring in FUAM

This report is designed to help users understand the behavior of On-Prem Data Gateways, identify potential bottlenecks, tracking query lifecycles.

Prerequisites

For ad-hoc report 'FUAM_Gateway_Monitoring_From_Files_Report'

• Access to the storage, where the Gateway Service writes the log files
• 'Additional Logging' on the Gateway service is recommended, but not required to use this module of FUAM

For report 'FUAM_Gateway_Monitoring_From_Lakehouse_Report' with continous data ingestion

• The Powershell scripts from Edgar Cotte needs to be configured (https://github.com/ecotte/rt-gateway-log/tree/main/PowerShell%20Script)
• The data has to be stored in FUAM Lakehouse files

Introduction

Typically, logs from the Gateway service are generated on Request base. A request (RequestId) is the unique identifier of an operation. Requests can be:

• DirectQuery queries
• Refreshes of semantic models/dataflows

This report focuses on those two type of requests, but also extracts System Counter information about the host and Gateway service.

Report screenshot

Query diagnostic

The query diagnostic drillthrough page provides deep insights about the lifecycle of a 'Request'.