Qlikview log analyser

[jansen28]

Hi Forum folks!

The problem we are facing in log file is that, if Qlikview document is having large amount of load script, it is currently difficult to find how much time each piece of the load script is taking time in document logs.

To resolve this we are plannig to implement a solution called "Document log analyser" which will analyse a set of qlikview document logs and capture the execution duration of each script statement in a reload.

Is there any keyword search in qlikivew where I could search for all keywords "loads" and "fields found" and extract that particular line and store it in a file. then compare 1st row and 2nd row and store the difference between separately....

Is this possible to do in qlikview? if yes, How to achieve it?

Any help greatly appreciated.

[marcus_sommer]

I have heard that somebody had already built such log-file analyzer but I can't remember who. But I think that approaches like these within in link fit better in a long term:

http://community.qlik.com/docs/DOC-7177#comment-20906

- Marcus

[rwunderlich · Accepted solution]

A Script Log Analysis tool is already written and freely available at:

Qlikview Cookbook: Script Log Analyzer http://qlikviewcookbook.com/recipes/download-info/script-log-analyzer/

-Rob

http://masterssummit.com

http://robwunderlich.com

[darrellbutler]

Rob,

Many thanks for your power tools, they're indispensable. I have one small issue with script log analyzer, it keeps falling down at line 1988 when trying to left Join onto LogSummary with the reason table not found. Any ideas what might be causing this ?

Kind regards

Darrell

[#5]

Hi Janani,

you might also find this

http://community.qlik.com/docs/DOC-6187

helpful for more customised audit logging to help you with sql load times, qvd store times, row counts etc etc

hope that helps

Joe

[Peter_Cammaert]

The ScriptLogAnalyzer reads logs with file mask *.qvw.log. Those are the real document logs generated by QV Desktop. It won't read QDS logs à la DocumentLog.txt, except if you rename them. And I don't know (yet) what happens with the wide timestamps in those logs.

[darrellbutler]

Peter,

Thanks for your reply, am I correct in assuming that the logs that are fed into the script analyzer are the logs saved to:

C:\ProgramData\Qliktech\DistributionService\1\Log and have generate logfile turned on at the document properties level ?

Thanks

[Peter_Cammaert]

QDS = QlikView Distribution Service. It won't read QDS logs for two reasons, I think:

• Those logs have the wrong filenames (not matching *.qvw.log)
• Their layout is different .QDS logs have wide (double) timestamp areas, while the Desktop logs don't.

Use the ScripLogAnalyzer only with actual document logs. In a server environment and with "Generate Log File" enabled, you can find them in the same directory as the published documents.

Rob Wunderlich maybe you can include an extra test in your wonderful tool: if table LogSummary is empty, skip the remainder of the script.

[darrellbutler]

Thanks for your help Peter, I understand which logs I should be using. However, it still seems to be falling down at the same point !

[Peter_Cammaert]

Well, I got it to work ok as soon as I pointed the ScriptLogAnalyser to a set of Desktop-generated logs. Just a moment, I'll try with logs in the server.