private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
This page contains content that we have migrated from Jetty 7 or Jetty 8 documentation into the correct format, but we have not yet audited it for technical accuracy in with Jetty 9. Be aware that examples or information contained on this page may be incorrect. Please check back soon as we continue improving the documentation, or submit corrections yourself to this page through Github. Thank you.
This page describes how to create log files at the server level and name them based on an arbitrary context. You do this with SLF4J + Logback + Jetty Webapp Logging in the mix. Find example projects for this feature at github:
https://github.com/jetty-project/jetty-and-logback-example
Table 9.1. GitHub Example Project
Modules | Description |
---|---|
/jetty-distro-with-logback-basic/ | Configures the jetty distribution with logback enabled at the server level with an example logback configuration. |
/jetty-distro-with-logback-sifting/ | Configures the jetty distribution with logback, centralized webapp logging, an MDC handler, and a sample logback configuration that performs sifting based on the incoming Host header on the requests. |
/jetty-slf4j-mdc-handler/ | Provides the SLF4J MDC key/value pairs that Jetty needs to perform the sample sifting. |
/jetty-slf4j-test-webapp/ | A sample webapp+servlet that accepts arbitrary values on a form POST and logs them via SLF4J, so that you can see the results of this example. |
See an error or something missing? Contribute to this documentation at Github!