TRACE will write information to the document log (the .log file in the same folder as the .qvw file, if enabled for the document). I don't know of any way to write trace information to the task log (which is, I think, what you mean by console log).
Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
Thats correct. We want to log additional information to Task Log. As in the Web browser we can ONLY have access to see the Task Log results. Unfortunately we have no access to the .log file it generates from .qvw. So this is a limitation I guess.
AFAIK the TaskLog is not written to from the reload engine (QVB.exe). I guess the QlikView Distribution Engine manages the TaskLog and the QDS has nothing whatsoever to do with the Load Script. It just waits for a job to finish and records the execution result. Separate processes...
This is stored in the Application Data Folder as specified in the QMC > System > Setup > Distribution Services > 1 (the number of the QDS as the name of the folder) > Log > Date (e.g.: today 20180508) > TaskLog.txt for what you refer as it appears on the QMC and DocumentLog.txt for the script execution.
TRACEs will be displayed on the latter.
You can create a QlikView application that reads and processes those logs (that's what the QlikView Governance Dashboard does).
I think Peter is right and it won't be possible because of the different processes. Maybe it's an alternatively to implement an application which reads all document-logs and which could be accessed per access point, for example with the tis tool from Rob: Script Log Analyzer v1.5 in German and Portuguese.
.png "Miguel_Angel_Baeyens"){kind=avatar}
