MyTimetable uses Logback as logging framework. By default it will only log warnings and errors, which will end up mytimetable.log in the Tomcat logs directory. This file is rotated every day and with every 50MB. Prior to version 3.0, log messages were sent to stdout (usually resulting in log messages being written to catalina.out or localhost.dd-MM-yy.log, depending on the Tomcat config). It is possible to specify your own Logback config file, using the following setting in the JAVA_OPTS of Tomcat:


More on the configuration file format can be found in the Logback manual.

MyTimetable comes with a development and debug Logback configuration file built-in, named logback-dev.xml. Use the following JAVA_OPTS setting to activate this configuration:


This will log almost all messages, so make sure to disable it when running in production, otherwise you will probably run out of disk space quickly.

Centralized log management with Logstash

MyTimetable supports logging to a Logstash centralized logging facility through SSL/TLS over TCP. To enable this feature, set the Logback configuration file to the built-in logback-logstash.xml. Use the following JAVA_OPTS settings to activate this feature:


The instance identifier will be passed to Logstash as a custom field, together with the application version and build identifier. These values are added to every log message and can be used for filtering purposes.

Note that when logging to Logstash is enabled, the application will also still log to the file defined in the built-in default Logback configuration.


Please allow traffic from your MyTimetable host(s) to for TCP port 4560. All logs are transmitted over SSL secured channels.

MyTimetable Consumer and Producer applications for External Calendaring

All of the abovementioned options also apply to the consumer and producer applications.

  • No labels