topic Re: Power BI Gateway Monitoring in Developer

Power BI Gateway Monitoring

BindiyaThota — Wed, 27 Nov 2024 10:17:33 GMT

Hi,

I am going through the gateway monitoring solution provided by Rui Romano, especially using disk template i.e. "Gateway Monitor - FromDisk.pbit". I also watched his video regarding the same (great content, BTW!). At about 20 minutes into the video, he explained how "DataLocation" parameter in the PBIT should point to folder path of gateway log export.

We usually export gateway logs from server on a monthly basis by passing the month start and end dates. I.e. open on-premises data gateway > "Diagnostics" tab > pass the "from" and "to" dates > click on "Export Logs" and copy the exported logs from gateway server to, say, my local machine (in below hierarchical folder structure). We have multiple gateway servers and do the same for each server.

Hierarchical folder structure: \Documents\AllGateways\<one folder per gateway>\<one folder per month>\<all exported logs>

Example:

\Documents\AllGateways\Gateway1\Sep2024\<all exported logs>

\Documents\AllGateways\Gateway1\Oct2024\<all exported logs>

\Documents\AllGateways\Gateway2\Sep2024\<all exported logs>

\Documents\AllGateways\Gateway2\Oct2024\<all exported logs>

Questions

If I want the PBIT to consider all historical data for all gateways, then

Will pointing PBIT to " \Documents\AllGateways" location consider all gateways?
Should the hierarchical folder structure contain all monthly exports per gateway or just the latest export?
Is exporting logs once a month (by passing first of month and last of month for "from" and "to" dates) good or should the cadence or date range be changed?

Any suggestions are much appreciated. Thanks!

Re: Power BI Gateway Monitoring

BindiyaThota — Wed, 27 Nov 2024 18:03:15 GMT

Is any one able to successfuly implement "disk template" by pointing to just one export from one gateway? I am running into errors when I try to load data.

Re: Power BI Gateway Monitoring

Anonymous — Thu, 28 Nov 2024 07:53:07 GMT

Hi , @BindiyaThota

Firstly, regarding your question about whether pointing the PBIT to the '\Documents\AllGateways' location will consider all gateways, I believe it is theoretically feasible. If you set the 'DataLocation' parameter to '\Documents\AllGateways', it should include all subfolders within that directory. This means that as long as the log files are organised in their respective folders, it will encompass logs from all gateways.

However, in my tests, my default input location was:

C:\Windows\ServiceProfiles\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway

Secondly, regarding your second question: if you want to analyse historical data, ideally, a hierarchical folder structure should include all monthly exports for each gateway. This way, you can track performance and issues over time.

Thirdly, exporting logs monthly is a good method for regular monitoring. However, if you encounter frequent issues or need more granular data, consider exporting logs more frequently, such as weekly. The date range should cover the entire period you want to analyse, so monthly exports with the first and last day of each month as the range are suitable for monthly monitoring.

Finally, if parameter input fails, you can refer to the following content:

The above are my personal opinions. If you have further questions, I recommend contacting the author directly, as they can provide more professional assistance.

RuiRomano (Rui Romano) · GitHub

Of course, if you have different opinions or new ideas, we welcome you to share them with us. I will always maintain a humble attitude and encourage you to post any further progress on this issue here.

Best Regards,

Leroy Lu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Power BI Gateway Monitoring

ChuckS — Fri, 06 Dec 2024 16:38:24 GMT

I came here looking for guidance on using the disk template provided by Rui Romano. I suspect changes in the gateway logs are creating errors within the template. Getting a lot of null to text errors as well as the JSON layout of the logs seems brocken. It looks as though the template has not been updated in a year.

Has anyone continued the work on this template or is there an alternative project out there?

Thanks,
Chuck