Controlling the QDF TRACE output

[#1]

Hallo,

when developing an QV App using QDF one will get a lot of output in the script status window while running the script in the QV Client App. Most off this output belongs to QDF and, because QDF often works like expected, this TRACE output is worth nothing (see screenshot, german mode).

So the idea is, that QDF should implement loglevels an app developer could set in order to fine tune the QDF TRACE output.

A good idea is to implement same levels as other logging frameworks like log4j or leg4net use. It should be possible to switch off any QDF tracing as well as use of different levels up to debug level.

It should be possible to change the level within the script, so that some load parts run in high, others in low logging/trace levels.

So in the above example for me only my custom coded TRACE 'OD:12.08.2015 12:08:37 (UTC): Script beendet' is usefull for me. Most of the other output is not interesting for me.

If you like this idea just vote for it.

Regards

Frank

(Update: I added my code here, because the comment editor of ideas in this web interface has got no advanced editor. It is just possible to add a picture or a video)

[#2]

Hallo Magnus,

as a "newbe" in Qlik I don't exactly know what is output that comes from Qlik itself and what comes from the QDF. So in respect to my screenshot you are right. Most of the output comes from AUTOGENERATE.

There is much more output in the QDF that comes directly out of Qlik and not out of TRACE statement within the Framework.

I have not seen any statement or configuration at document level to control the output QV itself does. I also have not seen any solution to switch off this QV logging within the script and switch it in again later in the script.

So as Damian said (see above): "This is community driven". So if somebody knows a solution for switching of the build in QV logging at some parts of a running script, feel invited to post it here.

If my posted solution is worth nothing, might be someone wants to use it anyway or QDF team decides to put it in the 4.Sub folder just like "7.CalendarGen" as a might be useful function-kit.

Regards

Frank

[Magnus_Berg]

Hi Frank, It will go into the framework so don't worry I was just thinking if we can enhance the function in some way? Btw good work! /Cheers

[cotiso_hanganu]

I was wondering, Magnus, have your team looked really deep into the work Rob Wunderlich did with his QVC ? Because it seems to me that at least some of his solutions should have been adopted in QDF...

Including the QVC.logging system (that might be a pretty simple solution to this issue.)

[#5]

Hallo Cotiso,

thx for your advice. I have never seen QVC before. It's new to me. To me it seems that it's a good idea to merge this two standards (QDF and QVC) into a big new framework.

But we have to be careful in mixing up words. So you know, frameworks like log4net  use the word "logging". QVC also uses this word but Qlik scripting uses "tracing". In QV the word "log" is used for an mathematic function we all know well since we have been at school.

(Ok, in .NET and c# it might be an mathematic fuction as well).

But I think we should use the word "trace".

And: QVC.Logging just knows three log level, the approach I posted uses five levels.

Regards

Frank