Team Studio Log Files
Depending on the log level set in chorus.properties, the volume of log files can vary substantially.
Supported log levels:
syslog
As an alternative to the log files listed above, all logs can be combined in one file using syslog as the logger. To turn on syslog as the logger, put logging.syslog = true in <chorus>/shared/chorus.properties.
logrotate
You can use the Linux command logrotate to rotate your log files and prevent accumulation. By running logrotate your_logrotate.conf from a cron job, you can ensure that the logs get rotated at preset intervals.
Here is an example of a your_logrotate.conf configuration file that rotates of all the important Team Studio log files:
daily rotate 4 copytruncate size 10M <chorus>/shared/log/production.log { } <chorus>/shared/log/nginx/access.log { } <chorus>/shared/log/nginx/error.log { } <chorus>/shared/log/solr-production.log { } <chorus>/shared/log/worker.production.log { } <chorus>/shared/log/scheduler.production.log { }
See the logrotate manual page for more information about the features of logrotate.
- Download Logs
Team Studio provides a download of the application logs. When contacting Support, please provide the logs. Having the logs makes it much easier for Support to assist you.