This plugin allows you to use Logback's very flexible access framework within Play.

Add JitPack resolver and the dependency

resolvers += "jitpack" at "https://jitpack.io"

libraryDependencies += "com.github.cardamo" % "play-logback-access" % "0.8.0"

Play version compatibility:

Add a configuration file to your conf/application.conf with something like:

logbackaccess.config.resource=logback-access.xml
play.modules.enabled += org.databrary.PlayLogbackAccessModule
play.filters.enabled += org.databrary.PlayLogbackAccessFilter

Then in conf/logback-access.xml:

<configuration>
  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    <encoder>
      <pattern>%t %D %s %h %b %A "%r" "%i{Referer}" "%i{User-Agent}"</pattern>
    </encoder>
  </appender>
  <appender-ref ref="STDOUT" />
</configuration>

(You can alternatively use logbackaccess.config.file or logbackaccess.config.url.)

You can read more about the supported patterns. Note that patterns requiring access to the full request body or response body (including content-length) do not currently provide useful data.

There is also a logbackaccess.context setting if you want it to use an execution context other than the default one.

The library is a Play Module which you need to enable by adding this to application's .conf file:

play.modules.enabled += "org.databrary.PlayLogbackAccessModule"

(if you experience any issues with dependency injection (esp. during tests), please try using PlayLogbackAccessLazyInjectModule which does the lazy dependency injection)

Inject PlayLogbackAccessApi into any class to gain access to the API. This exposes:

• log(requestTime: Long, request: RequestHeader, result: Result, user: Option[String]) - Manually log to the Access logger

Inject PlayLogbackAccessFilter to access a Filter (in 0.4 and earlier this was available as filter on the above)

Please refer to this page for previous docs.