QlikView Generate LogFile - Options for setting verbosity?

[Tyler_Waterfall]

Are there any verbosity options for the Generate Logfile for a .qvw reload?

I'd love to reduce the output by just listing the main points from a reload, as displayed in the status window, rather than such a verbose log that includes all SET and LET statements as well as the complete LOAD .... FROM (just tell me how many rows were loaded).

Maybe I've missed something obvious?

Thanks for your ideas!

[Qrishna]

You can try changing the level of logging verbosity

goto Management Console --> Set up -->Qlikview server

Edit: Not Sure about Qlikview Desktop verbosity Settings.(I guess theres nothing for verbosity settings)

[Tyler_Waterfall]

Thanks krishna - but this is for Desktop.

However, would that Server log setting reduce the verbosity of the app.qvw.log file if app.qvw were reloaded in Server?

[Qrishna]

1.Not Sure about Qlikview Desktop verbosity Settings.(I guess theres nothing for verbosity settings)

2. if app.qvw were reloaded in Server? Then Yes. I tried personally.

[maxgro]

It would be useful but AFAIK the answer is no.

I usually log the most important things to a different log using qlikview components library  (thanks to rwunderlich‌)

Script Diagnostics using Qlikview Components | Qlikview Cookbook

[rwunderlich]

Tyler,

There is no Document Log verbosity setting I'm aware of. What I wish we had was a statement to toggle logging on/off like:

LOG ON;

LOG OFF;

This would allow for suppression of logging from some of the bigger subroutines.

-Rob

[Peter_Cammaert]

Rob, Tyler has a good point in suggesting a verbosity level. It could be combined with your new statement, even as an optional parameter. Like in:

LOG ON 4;

which would mean: start/change logging to level 4 = only log SUB CALLs. With 0 meaning "log it all". And level 1 meaning "Log everything except LOAD column specs (replace them with a ...)"

Or a parameter as a bitmask where every bit toggles the logging of one particular type of activity.

[Tyler_Waterfall]

If you are working with a hidden script in which the load progress is also hidden from the .qvw.log --- Rob's solution is a nice approach. I started writing my own version and remembered this post.

Seems like we should fix the logging though to allow different verbosity, like OFF, INFO, TRACE, or DEBUG.