log.application.level configuration key specifies the severity threshold beneath which log messages will be discarded. Available values, in order of importance, are:
all can be used to log absolutely everything.
To completely disable the application log, use
Appenders direct log messages to various destinations, like files and/or the console. (The default configuration file logs only to the console.) There are several available appenders, which can be enabled or disabled in any combination.
ConsoleAppender logs to the console. Set the
log.application.ConsoleAppender.enabled configuration key to
false to enable or disable.
FileAppender logs to a single file. Use the
log.application.FileAppender.enabled key to enable or disable, and the
log.application.FileAppender.pathname key to set the absolute pathname of the log file.
RollingFileAppender logs to a file that rolls over periodically (to avoid creating a single huge file). Use the
log.application.RollingFileAppender.enabled key to enable or disable, and the
log.application.RollingFileAppender.pathname key to set the absolute pathname of the primary log file.
Currently, the only available rolling policy (
TimeBasedRollingPolicy, which rolls over the log file based on the value of
log.application.RollingFileAppender.TimeBasedRollingPolicy.max_history defines how many rolled-over log files will be kept.
SyslogAppender appends log messages to the syslog, managed by syslogd, on a local or remote host.
Access logs are written in the Common Log Format. To enable the access log, set the value of
true—or, if you are running Cantaloupe behind a reverse proxy server or in a Servlet container that manages its own access logs,
Access log appenders work the same as application log appenders.