Traffic Server provides several options for monitoring system performance and analyzing network traffic.
This chapter discusses the following topics:
Traffic Server provides the following tools to monitor system performance and analyze network traffic:
Traffic Server signals an alarm when it detects a problem. For example, the space allocated to event logs could be full or Traffic Server may not be able to write to a configuration file.
To configure Traffic Server to send an email to a specific address whenever an alarm occurs, follow the steps below:
records.config
file located in the Traffic Server config
directory.proxy.config.alarm_email
variable to the email address alarms will be routed to.records.config
file.bin
directory. traffic_line -x
to apply the configuration changes.Alarm messages are built into Traffic Server - you cannot change them. However, you can write a script file to execute certain actions when an alarm is signaled. Traffic Server provides a sample script file named example_alarm_bin.sh
in the bin
directory; simply modify the file to suit your needs.
You can use the Traffic Line command-line interface to view statistics about Traffic Server performance and web traffic. In addition to viewing statistics, you can also configure, stop, and restart the Traffic Server system. For additional information, refer to Configuring Traffic Server Using Traffic Line and Traffic Line Commands. You can view specific information about a Traffic Server node or cluster by specifying the variable that corresponds to the statistic you want to see.
bin
directory. traffic_line -r variable
variable
is the variable representing the information you want to view. For a list of variables you can specify, refer to Traffic Line Variables. traffic_line -r proxy.node.http.cache_hit_ratio
bin
directory is not in your path, then prepend the Traffic Line command with ./
(for example: ./traffic_line -r variable
).