Qlikiew\QlikTech\DistributionService\1\Log file getting bigger

[#1]

In the location Qlikiew\QlikTech\DistributionService\1\Log

Root_20131001 and so on with dates are getting bigger. Anyway to control them?

[Clever_Anjos]

Its a know issue

Schedule a task into your windows to cleanup this folder and C:\ProgramData\QlikTech\DistributionService\EDXResults that grows too much too

[#3]

my EDXresults isn't that big. Its about 3MB the whole dir

Where as - Each root file  in Qlikiew\QlikTech\DistributionService\1\Log is about 3GB.

Also  -  one question that I have is -

in the

System -> qlikview servers -> logging ->

Enable session loggin

enable performance logging every 5 mins

Enable event loggin

enable Audit loggin

Question:What is the regular practice to have the following checked? I have all above checked

Event log verbosity

low

medium  (checked)

high

May be if I change above it wont log that much - does any of these changes need qlikview services restart?

[#4]

Basically I want to control the amount it logs.

[Clever_Anjos]

Your setup is same as mine, I want to check what my users are doing (Audit loggin) and capture errors ( event loggin)

You can schedule a cleanup or create a manual process to 'check and delete' old files

C:\ProgramData\QlikTech\DistributionService\EDXResults is path not so big in size but keep thousands of files (Windows Servers seems not to 'like' it)

No need of restart your services

[#6 · Accepted solution]

just saw that - high tracing is enabled. I have disabled that.

disabled this piece -- so basically marked as false

Enabling
Trace Logs
-------------------

1. Open the Qlikview Distribution Service application folder (e.g. C:\Program
Files\QlikView\Publisher\Distribution Service )

2. Open "QlikviewDistributionService.exe.config" in Notepad

3. Locate the line reading "<!-- Setting this key to true will enable
logging used for debug. -->"

4. Change the value in the line below to "true"

5. Save and close. (Repeat for each cluster node if Cluster environment)

[#7]

This problem is happen on when u enable the performance monitor.

See the attached article for how to enable and disable the performance monitor.