Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
fdelacal
Specialist
Specialist

Non Generate Logfile

Hi all.

I have an app that generate a big log. field

There is any option like in qlikview (checkbox) to configure if we need to generate logfile or not.

I need a response for both the Sense Desktop version and the Sense server version.

Thanks in advance.

Kind regards.

9 Replies
fdelacal
Specialist
Specialist
Author

someone??

ToniKautto
Employee
Employee

Generally you don't want to disable logs, as they allow monitoring and analyzing of what is going on in your system.

Qlik Sense server moves logs to Archived logs folder, which means you can move that you can backup and/or delete the archive folder to lower the log file storage. It is also possible to alter verbosity levels for the server side services.

fdelacal
Specialist
Specialist
Author

Thanks Toni, as you say "Generally you don't want to disable logs". But in this situation i need it.

ToniKautto
Employee
Employee

May I ask what the reason is?

Typically we expect enough storage to manage the current logs.

acardella
Partner - Creator
Partner - Creator

Hi,

you can try with a scheduled batch to erase log files. You can find log path in QMC --> ServiceCluster

Bye

log.png

fdelacal
Specialist
Specialist
Author

Hi acardella‌ Thanks for the comment, i Know this possibility, but i need no generate it.

Kind Regards-

ToniKautto
Employee
Employee

Can you expand on what problem the log file is causing? I currently do not understand the need to avoid it.

JustinDallas
Specialist III
Specialist III

Push come to shove, you can create a Powershell script to delete the entries in the log folder.    This Powershell script can be set to run as a Windows task for whatever interval you need (every minute, every hour).  It's not as good as not creating the log file, but it's an idea.

One problem is that if someone is currently reading/writing the file and has obtained a lock (the QlikSense server) you might not be able to delete it.  Then, you might have to try other things.

Using the Clear-Content Cmdlet