topic Re: Qliksense Log Files have filled up server in Management & Governance

Qliksense Log Files have filled up server

timsaddler — Tue, 30 Jun 2015 06:30:13 GMT

Hello

How do I reduce the amount/size of logs?

I've run out of disk space.

This location seems to be the problem

C:\ProgramData\Qlik\Sense\Log\Script\

Can someone point me in the direction of which setting I can change

thanks

Re: Qliksense Log Files have filled up server

Michael_Tarallo — Thu, 02 Jul 2015 11:51:40 GMT

Hi Tim,

Sorry for the delay - feel free to *bump* a post up - if you do not get a reply, so it may be visible again at the top of the list.

See this topic in the help fie:

http://help.qlik.com/sense/2.0/en-US/online/#../Subsystems/PlanningQlikSenseDeployments/Content/Server/Server-Logging.ht…

Storage

The default log files are stored in folders under %ProgramData%\Qlik\Sense\Log. The local log configuration file can be used to set up the logging so that the log files are also stored in another location.

You can change the logging levels - here: QMC->Engines->Central - look for Logging.

Let us know how you do.

Please mark the appropriate replies as CORRECT / HELPFUL so our team and other members know that your question(s) has been answered to your satisfaction.

Regards,

Mike Tarallo

Qlik

Re: Qliksense Log Files have filled up server

timsaddler — Thu, 02 Jul 2015 12:22:17 GMT

my screen doesn't look like yours so maybe I have a different qliksense version?

I haven't quite got round to upgrading to 2.0 (next week hopefully)

I've turned all to Info in my version

Am I right in thinking that upgrading Qlikview or Qliksense server by default turns logging back up to maximum as I seemed to caught out on this with this on Qlikview server SR11 upgrade ?

Re: Qliksense Log Files have filled up server

timsaddler — Fri, 13 Nov 2015 15:38:31 GMT

About a month ago i did upgrade to 2.1.1 and now my server has filled up with logfiles.

Can i delete Trace Log files or does this "destroy" the Operation Monitor Dashboard which is what i am being told by 3rd party support?

I enclose a screenshot as i also see that every 8 hours an 8 meg file is created ?

I'm not sure what this is ?

As for the logging protocol , i have them set to "info" which i thought was the smallest log produced?

I enclose another screenshot

Re: Qliksense Log Files have filled up server

Michael_Tarallo — Fri, 13 Nov 2015 15:47:17 GMT

Hi Tim - I added twa‌ - to this discussion - Hi Tyler any suggestions?

Mike

Re: Qliksense Log Files have filled up server

timsaddler — Fri, 13 Nov 2015 16:15:59 GMT

Great Mike - we are planning to roll out Qliksense to our first users at the end of the month so want to keep on top of this to avoid "user experience issues"

Re: Qliksense Log Files have filled up server

Tyler_Waterfall — Fri, 13 Nov 2015 16:41:12 GMT

Tim,

You can remove all logs you want, but that will remove the history (which might not be a big deal at this point.)

I recommend you turn off the QIX log (can get large VERY fast) and the traffic log. Neither is used by the Monitoring Apps (ie Operations Monitor) and these are typically just used for deep dive troubleshooting.

Concerning the Log\Script folder, we currently do not have an automated way to control the files there. You can remove those at will, keeping in mind that you will lose the nitty gritty details for each reload execution (which again might not be a big deal).

Also note that these script logs are archived in the Qlik\Sense\Repository\Archived Logs\[server]\Script folder and could be removed from there too.

Re: Qliksense Log Files have filled up server

timsaddler — Fri, 13 Nov 2015 16:53:51 GMT

Great Tyler - many thanks for the prompt response .

i'll implement on monday - now off home for the weekend

Re: Qliksense Log Files have filled up server

timsaddler — Mon, 16 Nov 2015 09:53:53 GMT

One other point Tyler, if i change the performance log interval from 5 minutes to 10 mins , then presumably this will halve the amount of logs ?

Are there any disadvantages of doing this ?

Thanks

Re: Qliksense Log Files have filled up server

Tyler_Waterfall — Mon, 16 Nov 2015 13:21:39 GMT

Doing so would reduce the number of engine logs. The downside is less granular view of engine performance. You might not have any issue doing that initially. If the time comes when you need more granular detail on engine activity, change it back to 5 or 1 minute interval.

The biggest bang for your buck is to turn off the QIX log and the traffic log, and then periodically remove or zip up and move the script log files.

Re: Qliksense Log Files have filled up server

timsaddler — Mon, 16 Nov 2015 13:29:14 GMT

good answer - i must have been psychic cos that's just what i did - zip the script log files

That returned me another 3 GB

I'll stick with 5 mins for the time being i think.

Thanks again

Re: Qliksense Log Files have filled up server

deepanshu_chamo — Mon, 19 Mar 2018 06:20:41 GMT

Hello Tyler

I am too facing the same issue. The Achieved logs keeps on increasing and it takes our Maximum Disk Space for Production Env.

Could you please help me to know what is the Ideal Time Frame to keep the Logs for any analyzing perspective.

Thanks

Deepanshu

Re: Qliksense Log Files have filled up server

Tyler_Waterfall — Mon, 23 Apr 2018 11:09:04 GMT

Hi deepanshu.chamoli‌ - There is no one "ideal" timeframe for everyone. But you might consider a few things -

1- How much history do you want to see for sessions and usage (licensing)? 12 months seems typical

2- How likely are you to go back further than 3 months ago to troubleshoot some issue?

3- How many months of performance measures would help you understand capacity needs and anticipate the need for expansion?

I think the ideal situation is to retain long history (12-24 months) of certain logs (for licensing, app usage), and short history (3-6 months) for troubleshooting logs.

However, keeping this kind of mixed history would be a manual process unless you devise an automated script to accomplish this.

Candidates for Longer history -

- Scheduler > Trace > TaskExecutionHistory

- Engine > Trace > Session_Engine

- Repository >.. > AuditSecurity_Repository

- Proxy > .. > AuditSecurity_Proxy

- Engine > Trace > Performance