Team Studio Log Files

Depending on the log level set in chorus.properties, the volume of log files can vary substantially.

Supported log levels:

  • debug
  • info
  • warn
  • error
  • fatal
Log name File path Description
production.log <chorus-root>/shared/log/production.log Contains information about requests sent to the Team Studio web server, and various debugging information such as server errors, file not found errors, and permission denied messages.
worker.production.log <chorus-root>/shared/log/worker.production.log Contains logs for the background worker threads that Team Studio uses to perform various asynchronous tasks such as database imports and checking instance statuses.
scheduler.production.log <chorus-root>/shared/log/scheduler.production.log Contains information about jobs that the scheduler issues to different background workers. This mainly shows that a task was scheduled. See worker.production.log for more detailed information about what happened during execution of a task.
solr-production.log <chorus-root>/shared/log/solr-production.log Contains information about solr search queries issued against Team Studio.

nginx

nginx maintains access.log and error.log files in <chorus-root>/shared/log/nginx.

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.

Note: If you use syslog, you do not need to rotate your logs manually; syslog rotates the log files for you.