We are in the process of migrating from Qlik View to Qlik Sense, and I'm having a hard time finding some of the information that I'm looking for in the log files. The following are a list of log files I'm using in Qlik View that I need to find the equivalent of in Qlik Sense: c$\ProgramData\QlikTech\ManagementService\QVPR\DocumentTask.xml c$\ProgramData\Qliktech\DistributionService\TaskExecutionHistory\ c$\ProgramData\QlikTech\DistributionService\1\Log\
Does anyone know where I can find these (or something like them) in Qlik Sense?
I read through these already, and the only thing I found was c$\ProgramData\Qlik\Sense\Log\Scheduler\Trace\<Server>_TaskExecution_Scheduler.txt which looks pretty close to the DocumentTask.xml file. The others I haven't had any luck finding.
I found what I needed for the first two: c$\ProgramData\QlikTech\ManagementService\QVPR\DocumentTask.xml c$\ProgramData\Qliktech\DistributionService\TaskExecutionHistory\
By looking at the default sources on the Qlik Sense Server, I was able to map to these files for the above: lib://ServerLogFolder/Scheduler/Trace/*TaskExecution_Scheduler.txt lib://ArchivedLogsFolder/<Server>/Scheduler/Trace/*TaskExecution_Scheduler*.log
What I haven't been able to find is an equivalent for the files in: c$\ProgramData\QlikTech\DistributionService\1\Log\
I was using those to determine HOW a job was run (EDX trigger, manually, scheduled, etc.).
As others have said, there aren't direct ports of every element. The Scheduler is analogous to QDS in QlikView in that it just the launcher for another process to handle the reload (qvb.exe in QlikView, Engine.exe in Qlik Sense).
> I was using those to determine HOW a job was run (EDX trigger, manually, scheduled, etc.).
Inside of Qlik Sense this concept makes no sense. Everything is built on RESTful APIs when it comes to the administration of Qlik Sense. This means the internal process of triggering a task to start is exactly the same as an integration layer which is calling the API directly.