
106
Chapter 12
Working with Log Files
o
The origin servers you want to log (if the servers tag is used, Traffic Server will only log transactions
from the origin servers listed, otherwise, transactions from all origin servers are logged).
To generate XML-based custom log files:
1. Access Traffic Manager from your browser (refer to
Accessing Traffic Manager‚ on page 8
).
2. On the Configure tab, click the Logging button.
3. Scroll to the Custom Logs section of the Logging page (shown below).
4. Select the Enabled: On button.
5. Select the XML button.
6. Click the Make These Changes button, then exit Traffic Manager.
7. Telnet into the HP web cache appliance and select Shell Access as described in
Overview of Access
Methods‚ on page 7
.
8. Open the
records.config
file located in Traffic Server’s
config
directory with Vi.
9. Search for the following string:
CONFIG proxy.config.log2.xml_config_file STRING
10. After
STRING
, enter the name of the XML-based logging configuration file.
By default, this is
logs_xml.config
, located in the
config
directory.
11. Save and close the
records.config
file.
12. Open the
logs_xml.config
file with Vi.
13. Add
LogFormat
,
LogFilter
, and
LogObject
specifications to the configuration file.
For detailed information about the
logs_xml.config
file and associated object specifications, see
logs_xml.config‚ on page 171
.
14. Save and close the
logs_xml.config
file.
15. Run the command
traffic_line -x
to apply the configuration changes.
Creating summary log files
Traffic Server performs several hundred operations per second, therefore, event log files can grow quickly to
large sizes. Using SQL-like aggregate operators, you can configure Traffic Server to create summary log files
that summarize a set of log entries over a specified period of time. This can significantly reduce the size of the
log files generated.
You generate a summary log file by creating a
LogFormat
object in the XML-based logging configuration
file (
logs_xml.config
) using the following SQL-like aggregate operators:
NOTE
To generate a custom log file, you must specify at least one
LogObject
definition. One
log file is produced for each
LogObject
definition.