Dear all,
when using the Basex Xquery server (9.7.3) we see that logs such as [1] are produced for every query execution.
Since we have a scenario which involves polling and thus we have a lot of query executions the log files increase to hundreds om MBs during a day.
This makes them unmanageable and even cause dba UI to crash with OOM exceptions when opening the logs page.
Is there a way to disable this logging (without affecting other logs such as HTTP)?
Is it really necessary to log server side query executions at this grain by default? Maybe it could be made optional?
Thanks for any support.
Regards,
Marco.
[1] 12:22:27.849 10.0.4.15:50424 admin OK 0.02 CLOSE[0] 12:22:27.848 10.0.4.15:50434 admin OK 1.40 FULL[0] 12:22:27.848 10.0.4.15:50424 admin OK 0.83 FULL[0] 12:22:27.847 10.0.4.15:50420 admin OK 0.05 CLOSE[0] 12:22:27.847 10.0.4.15:50412 admin OK 0.04 CLOSE[0] 12:22:27.847 10.0.4.15:50434 admin OK 0.05 BIND[0] db=infrastructures as xs:string 12:22:27.846 10.0.4.15:50410 admin OK 0.22 CLOSE[0] 12:22:27.846 10.0.4.15:50434 admin OK 0.06 BIND[0] id=ontheroad-lxd as xs:string 12:22:27.846 10.0.4.15:50424 admin OK 0.05 BIND[0] db=infrastructures as xs:string 12:22:27.846 10.0.4.15:50420 admin OK 0.62 FULL[0] 12:22:27.846 10.0.4.15:50412 admin OK 0.90 FULL[0] 12:22:27.846 10.0.4.15:50424 admin OK 0.06 BIND[0] id=ontheroad-lxd as xs:string 12:22:27.845 10.0.4.15:50380 admin OK 0.02 CLOSE[0] 12:22:27.845 10.0.4.15:50366 admin OK 0.01 CLOSE[0] 12:22:27.845 10.0.4.15:50402 admin OK 0.02 CLOSE[0] 12:22:27.845 10.0.4.15:50420 admin OK 0.04 BIND[0] db=infrastructures as xs:string 12:22:27.845 10.0.4.15:50386 admin OK 0.02 CLOSE[0] 12:22:27.845 10.0.4.15:50410 admin OK 0.88 FULL[0] 12:22:27.845 10.0.4.15:50420 admin OK 0.06 BIND[0] id=ontheroad-lxd as xs:string 12:22:27.845 10.0.4.15:50412 admin OK 0.04 BIND[0] db=infrastructures as xs:string 12:22:27.845 10.0.4.15:50434 admin OK 0.04 QUERY[0] declare variable $id external; declare variable $db external; db:open($db)[json/id = $id]