
171
Appendix D
Configuration Files
WELF (WebTrends Enhanced Log Format)
Traffic Server supports WELF, the WebTrends Enhanced Log format, so that you can analyze Traffic Server
log files with WebTrends reporting tools. A predefined custom format for WELF is provided in the
logs.config
file. To create a WELF format log file, comment out the following section at the end of the file
and replace
<
FORMAT_ID
>
with a unique integer.
#format:enabled:<FORMAT_ID>:welf:id=firewall time="%<cqtd> %<cqtt>" fw=%<phn>
pri=6 proto=%<cqus> duration=%<ttmsf> sent=%<psql> rcvd=%<cqhl> src=%<chi>
dst=%<shi> dstname=%<shn> user=%<caun> op=%<cqhm> arg="%<cqup>" result=%<pssc>
ref="%<{Referer}cqh>" agent="%<{user-agent}cqh>" cache=%<crc>:welf:ASCII:none
#
log_hosts.config
To record HTTP/FTP transactions for different origin servers in separate log files, you must list each origin
server’s hostname in the
log_hosts.config
file.
Format
Each line in the
log_hosts.config
file has the following format:
hostname
where
hostname
is the hostname of the origin server.
Example
The following lines in the
log_hosts.config
file configure Traffic Server to create a separate log files
containing all HTTP/FTP transactions for the origin servers
webserver1, webserver2,
and
webserver3
if the HTTP host log splitting option is enabled.
webserver1
webserver2
webserver3
For information about enabling the HTTP host log splitting option, refer to
HTTP host log splitting‚ on
page 112
.
logs_xml.config
This is the configuration file for the most configurable form of Traffic Server logging. This file defines log
files, their formats, filters, as well as processing options. The format of this file is modeled after XML, the
eXtensible Markup Language.
Use this file instead of the
logs.config
file when you need to establish fine-grained control over the format
and disposition of custom transaction logs. You can enable or disable this extended format logging by editing
the following variable in the
records.config
file:
NOTE
HP recommends that you use the same
log_hosts.config
file on every Traffic
Server node in your cluster.
IMPORTANT
After you modify the
log_hosts.config
file, Traffic Manager has to reread the
configuration files. Run the
traffic_line -x
command. If you are running a cluster,
you need only run the command for one node; the changes will propagate.