-
Notifications
You must be signed in to change notification settings - Fork 0
SettingsLogger
Play 2.0 uses logback as its logging engine.
The easiest way to configure the logging level is to use the logger
key in your conf/application.conf
file.
Play defines a default application
logger for your application, which is automatically used when you use the default Logger
operations.
# Root logger:
logger=ERROR
# Logger used by the framework:
logger.play=INFO
# Logger provided to your application:
logger.application=DEBUG
The root logger configuration affects all log calls, rather than requiring custom logging levels. Additionally, if you want to enable the logging level for a specific library, you can specify it here. For example to enable TRACE
log level for Spring, you could add:
logger.org.springframework=TRACE
The default is to define two appenders, one dispatched to the standard out stream, and the other to the logs/application.log
file.
If you want to fully customize logback, just define a conf/application-logger.xml
configuration file. Here is the default configuration file used by Play:
<configuration>
<conversionRule conversionWord="coloredLevel" converterClass="play.api.Logger$ColoredLevel" />
<appender name="FILE" class="ch.qos.logback.core.FileAppender">
<file>${application.home}/logs/application.log</file>
<encoder>
<pattern>%date - [%level] - from %logger in %thread %n%message%n%xException%n</pattern>
</encoder>
</appender>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%coloredLevel %logger{15} - %message%n%xException{5}</pattern>
</encoder>
</appender>
<logger name="play" level="INFO" />
<logger name="application" level="INFO" />
<root level="ERROR">
<appender-ref ref="STDOUT" />
<appender-ref ref="FILE" />
</root>
</configuration>
You can also specify another logback configuration file via a System property. It is particulary useful when running in production.
Specify another logback configuration file to be loaded from the classpath:
$ start -Dlogger.resource=prod-logger.xml
Specify another logback configuration file to be loaded from the file system:
$ start -Dlogger.file=/opt/prod/logger.xml
Specify another logback configuration file to be loaded from an URL:
$ start -Dlogger.url=http://conf.mycompany.com/logger.xml
- Configuration file syntax and features
- Configuring the JDBC connection pool
- Configuring Play's thread pools
- Configuring logging
- Installing Play
- Creating a new application
- Anatomy of a Play application
- Using the Play console
- Setting-up your preferred IDE
- Sample applications