QueueMetrics produces a detailed activity at the container level that lets us diagnose performance issues and technical errors.
These logs are NOT automatically deleted in any way so they may end up filling all of the disk space if they are never purged.
As disk space is very cheap these days, we advise in any case to make a backup before removing files and data - what is removed cannot be restored.The system log
The system log is where QM keeps information about actions performed and failed and successful log-ons. You can purge it manually by running the following queries:
mysql> delete from arch_syslog where sys_dt_creazione < DATE_SUB( NOW(), INTERVAL 90 DAY );
Query OK, 756 rows affected (0.04 sec)
mysql> optimize table arch_syslog;
Optimizing is very important as it reclaims disk space. The query above deletes all records older than 90 days.Tomcat log files
Tomcat keeps a running log of all activity and errors. In a standard QM installation, it should be located in /usr/local/queuemetrics/tomcat/logs
[root@qm ~]# du --human-readable /usr/local/queuemetrics/tomcat/logs/
[root@qm ~]# cd /usr/local/queuemetrics/tomcat/logs/
[root@qm logs]# /etc/init.d/queuemetrics stop
[root@qm logs]# rm -f catalina.out
[root@qm logs]# rm -f localhost*.txt
[root@qm logs]# /etc/init.d/queuemetrics start
[root@qm logs]# du --human-readable /usr/local/queuemetrics/tomcat/logs/
As you can see, it is necessary to stop Tomcat in order to do this.
If you want, it is possible to control the logging made by Tomcat or turn it off altogether - see section "Logs and Logging" of the WombatDialer User Manual at http://wombatdialer.com/manuals/WD_UserManual-chunked/ar01s07.html#_logs_and_logging