On-Premises Data Gateway monitoring strategy, why do I care?
You have carefully prepared your fantastic reports with Power BI Desktop and the time has come to share them with your colleagues. Obviously you don’t want to simply show the visuals frozen at the release state, but you want the underlying dataset to be refreshable so that the data visuals show up-to-date information. Therefore, after publishing the report on Power BI Service, you will certainly take care to install and configure an On-premises Data Gateway in Enterprise mode on a machine from which the data source is reachable, so that you can schedule a dataset refresh appropriately.
Whenever you are dealing with a Data Gateway no matter how powerful your sources and Power BI capacity are, the Gateway is a crucial part of your architecture and you should be ready to react if problems arise.
During this session we’ll see how to establish monitoring and troubleshooting strategy accordingly leveraging default logging and building a comprehensive solution.
Back in 2010 I started working in Information Technology.
After a brief experience as ERP Consultant, I moved into Data Realm.
I spent these years exploring Data world from different points of view, both as DBA and Business Intelligence Engineer.
I’m a Microsoft Certified Professional (MCP), Microsoft Data Analyst Associate, Microsoft Technology Associate (MTA), Microsoft Certified Solution Associate (MCSA) in database, BI and Azure areas.
Microsoft MVP for Data Platform category.
I’m one of the leaders of Power BI User Group in Italy and I’d been speaker during the Power Platform World Tour and Power Platform Bootcamp stops in Italy.
I’m also speaker during Azure Saturday, SQL Saturday and Data Saturday events in Europe.
Last but not least, Hard Rock and Heavy Metal addicted!
|18u30||Welcome and introductions|
|18u30||On-Premises Data Gateway monitoring strategy, why do I care? (75 minutes)|