Forum Discussion
Power BI VNet Gateway Diagnostics Logs - Automated Reporting and Failure Analysis
You can follow these instructions to download vnet gateway logs from manage gateways page
https://learn.microsoft.com/en-us/data-integration/vnet/data-gateway-download-diagnostics
however, I am not aware of any automated way to extract logs. I believe at present its a manual process only.
You can reachout to the support team and check with them, and then create an idea in ideas forum
You can read my blogs here:https://www.techietips.co.in/
Connect on LinkedIn
Did I answer your question? Mark my post as a solution! If I helped you, click on the Thumbs Up to give Kudos.
Proud to be a Super User!
Resolver IIYes, this is possible, although Microsoft doesn't currently provide a native continuous export mechanism for VNet Gateway diagnostic logs. The logs can be downloaded from the Manage connections and gateways page and include System Counters, Mashup Logs, Query Execution Report, and Resource Consumption data. System Counters and Query Execution Reports are provided in Parquet format, while Mashup Logs are JSONL, which makes them relatively straightforward to ingest into Fabric, Azure Data Lake, or a Power BI model for analysis.
For a scalable monitoring solution, I'd recommend automating the ingestion of downloaded logs into a centralized storage layer (such as OneLake or ADLS), then building a semantic model and Power BI dashboard around key metrics including gateway CPU/memory utilization, query duration, refresh failures, throttling events, container restarts, and connectivity issues. Several organizations have also adopted community and Microsoft-backed gateway monitoring solutions that centralize gateway telemetry and provide historical trend analysis.
If you're already using Fabric, a good architecture would be Gateway Logs → OneLake/Data Lake → Fabric Dataflow/Notebook → Semantic Model → Power BI Dashboard & Alerts. This gives you both operational monitoring and long-term trend analysis for capacity planning and troubleshooting.