Version: 9.4.5.v20170502 |
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 for sponsored feature development
Request logs are a record of the requests that the server has processed. There is one entry per request received, and commonly in the standard NCSA format, so you can use tools like Webalizer to analyze them conveniently.
A standard request log entry includes the client IP address, date, method, URL, result, size, referrer, user agent and latency. For example:
123.4.5.6 - - [20/Jul/2016:10:16:17 +0000] "GET /jetty/tut/XmlConfiguration.html HTTP/1.1" 200 76793 "http://localhost:8080/jetty/tut/logging.html" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040614 Firefox/0.8" 342
Jetty provides an implementation called NCSARequestLog
which supports the NCSA format in files that will roll over on a daily basis.
The Logback Project offers another implementation of a RequestLog
interface, providing rich and powerful HTTP-access log functionality.
If neither of these options meets your needs, you can implement a custom request logger by implementing Jetty’s RequestLog.java
interface and plugging it in similar to the NCSARequestLog
, as shown below.
To enable the Request Log module for the entire server via the Jetty distribution, it first needs to be enabled on the command line:
$ java -jar ../start.jar --add-to-start=requestlog INFO: requestlog initialised in ${jetty.base}/start.d/requestlog.ini MKDIR: ${jetty.base}/logs INFO: Base directory was modified
The above command will add a new requestlog.ini
file to your {$jetty.base}/start.d
directory.
Note
By default, request logs are not set to be appended, meaning a the log file is wiped clean upon sever restart. You can change this setting by editing the
requestlog.ini
and un-commenting the line that readsjetty.requestlog.append=true
.
The equivalent code for embedded usages of Jetty is:
NCSARequestLog requestLog = new NCSARequestLog("/var/logs/jetty/jetty-yyyy_mm_dd.request.log");
requestLog.setAppend(true);
requestLog.setExtended(false);
requestLog.setLogTimeZone("GMT");
requestLog.setLogLatency(true);
requestLog.setRetainDays("90");
server.setRequestLog(requestLog);
This configures a request log in {$jetty.home}/logs
with filenames including the date.
Existing log files are appended to and the extended NCSA format is used in the GMT time zone.
The above configuration enables Log Latency, which is the amount of time it took the server to handle the request. This value is measured in milliseconds and is appended to the the log file for each request.
You can also customize the number of days you wish to keep request logs.
By default, log files are kept for 90 days before being deleted.
The value for retainDays
(xml) or setRetainDays
(Java) should be configured as 1 + n days.
For example, if you wanted to keep the logs for the current day and the day prior you would set the retainDays
(or setRetainDays
) value to 2.
To examine more configuration options, see NCSARequestLog.java.
To configure a separate request log for specific a web application, add the following to the context XML file.
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
...
<Call name="insertHandler">
<Arg>
<New id="RequestLog" class="org.eclipse.jetty.server.handler.RequestLogHandler">
<Set name="requestLog">
<New id="RequestLogImpl" class="org.eclipse.jetty.server.NCSARequestLog">
<Set name="filename"><Property name="jetty.logs" default="./logs"/>/test-yyyy_mm_dd.request.log</Set>
<Set name="filenameDateFormat">yyyy_MM_dd</Set>
<Set name="LogTimeZone">GMT</Set>
<Set name="retainDays">90</Set>
<Set name="append">true</Set>
<Set name="LogLatency">true</Set>
</New>
</Set>
</New>
</Arg>
</Call>
...
</Configure>