WebSphere Virtual Enterprise (formerly Operations Optimization), Version 6.1
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Custom logs overview

Custom logs give you the flexibility as to what data is captured, the manner in which it is displayed, and the ability to have multiple conditional logs. You can create rulesets to specify the data to include, the order of how it is displayed, the conditional logic to filter which requests are included, and the number and names of log files.

Custom rules

Custom logs can be configured by using rules. Each rule has a condition which must be met in order for the corresponding action to be taken.

Log action format

The action's value attribute contains a set of arguments to indicate the filename and format of the log. To create multiple logs in the value attribute, delimit the arguments with a @. The first argument for the log action is the name of the log file, relative to the ODR 's logs directory. The following arguments are parameters to specify what information to place into the log. The data is shown in the order that the parameters are specified.

Table 1. Custom log parameters
Parameter Description
%a Remote IP -address.
%A Local IP - address.
%B Bytes sent, excluding HTTP headers.
%b Bytes sent, excluding HTTP headers. In CLF format, that is, a '-' rather than a zero when no bytes are sent.
%{FOOBAR}C The contents of the cookie in the request sent to the server.
%{FOOBAR}i The contents of Foobar: header line(s) in the request sent to the server.
% I Bytes received, including request and headers, cannot be zero.
%{FOOBAR}e The contents of the debug argument ("-D") FOOBAR specified for the JVM of the ODR process.
%h Remote host.
%H The request protocol HTTP or HTTPS.
%m The request method.
%{FOOBAR}o The contents of Foobar, header line(s) in the reply.
%O Bytes sent, including headers; the number cannot be zero.
%p The canonical port of the server serving the request.
%q The query string, pepended with a ? if a query string exists. Otherwise, it is an empty string.
%r First line of request.
%R Response time in milliseconds. Combined time spent in ODR and application server.
%s Status, HTTP response code, that is, 503, 404, 200.
%t Time, in common log format time format, standard English format.
%{format}t The time, in the form given by format, which should be in strftime(3) format. Potentially localized.
%T The time taken to serve the request, in milliseconds.
%U The URL path requested, not including any query string.
%v The canonical ServerName of the server serving the request.
%z Destination IP-address.
%Z Destination server name (cell/node/server).



Related tasks
[Version 6.1.0.5 and later] Configuring custom logs
Related reference
manageODR.py script
Concept topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 6:17:06 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ops.doc/info/odoe_task/cxdcustomlog.html