You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by ig...@apache.org on 2011/05/15 02:54:33 UTC

svn commit: r1103261 - in /trafficserver/site/branches/ats-cms/content/docs/trunk/admin: getting-started/index.en.mdtext monitoring-traffic/index.en.mdtext

Author: igalic
Date: Sun May 15 00:54:33 2011
New Revision: 1103261

URL: http://svn.apache.org/viewvc?rev=1103261&view=rev
Log:
Fix up Monitoring chapter, minor fixes in "Getting Started"

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/getting-started/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/getting-started/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/getting-started/index.en.mdtext?rev=1103261&r1=1103260&r2=1103261&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/getting-started/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/getting-started/index.en.mdtext Sun May 15 00:54:33 2011
@@ -26,10 +26,10 @@ for [build instructions](https://cwiki.a
 After you have installed Traffic Server on your system, you can do any of the
 following:
 
-* [Start Traffic Server](#StartingTrafficEdge)
-* [Start Traffic Line](#StartingTrafficLine)
-* [Start Traffic Shell](#StartingTrafficShell)
-* [Stop Traffic Server](#StoppingTrafficEdge)
+* [Start Traffic Server](#StartTS)
+* [Start Traffic Line](#StartTrafficLine)
+* [Start Traffic Shell](#StartTrafficShell)
+* [Stop Traffic Server](#StopTS)
 
 ## Start Traffic Server ## {#StartTS}
 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext?rev=1103261&r1=1103260&r2=1103261&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext Sun May 15 00:54:33 2011
@@ -24,20 +24,25 @@ analyzing network traffic.
 
 This chapter discusses the following topics:
 
-* [Traffic Server Monitoring Tools](#TrafficEdgeMonitoringTools)
+* [Traffic Server Monitoring Tools](#TSMonitoringTools)
 * [Working with Traffic Manager Alarms](#WorkingTrafficManagerAlarms)
 * [Viewing Statistics from Traffic Line](#ViewingStatisticsTrafficLine)
 
 ## Traffic Server Monitoring Tools ## {#TSMonitoringTools}
 
- Traffic Server provides the following tools to monitor system performance 
+Traffic Server provides the following tools to monitor system performance 
 and analyze network traffic:
 
-* Traffic Server can send email that's triggered by alarms that signal any detected failure conditions; refer to [Working with Traffic Manager Alarms](#WorkingTrafficManagerAlarms).
-* The Traffic Line command-line interface provides an alternative method of viewing Traffic Server performance and network traffic information; refer to [Viewing Statistics from Traffic Line](#ViewingStatisticsTrafficLine).
-* The Traffic Shell command-line tool provides yet another alternative method of viewing Traffic Server performance and network traffic information; refer to [Starting Traffic Shell](getstart.htm#StartingTrafficShell).
+* Traffic Server can send email that's triggered by alarms that signal any
+  detected failure conditions; refer to [Working with Traffic Manager Alarms](#WorkingTrafficManagerAlarms).
+* The Traffic Line command-line interface provides an alternative method of
+  viewing Traffic Server performance and network traffic information;
+  refer to [Viewing Statistics from Traffic Line](#ViewingStatisticsTrafficLine).
+* The Traffic Shell command-line tool provides yet another alternative method
+  of viewing Traffic Server performance and network traffic information;
+  refer to [Starting Traffic Shell](../getting-started#StartTrafficShell).
 
-## Working with Traffic Manager Alarms ## {#WorkingwithTrafficManagerAlarms}
+## Working with Traffic Manager Alarms ## {#WorkingTrafficManagerAlarms}
 
 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 
@@ -48,11 +53,9 @@ 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:
 
-1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory.
-2. Set the `_proxy.config.alarm_email_` variable to the email address alarms will be routed to.
-3. Save and close the `records.config` file.
-4. Navigate to the Traffic Server `bin` directory.   
-
+1. In the [`records.config`](../configuration-files/records.config) file
+2. Set the [_`proxy.config.alarm_email`_](../configuration-files/records.config#proxy.config.alarm_email)
+   variable to the email address alarms will be routed to.
 5. Run the command `traffic_line -x` to apply the configuration changes.
 
 ### Using a Script File for Alarms ### {#UsingaScriptFileforAlarms}
@@ -62,25 +65,31 @@ you can write a script file to execute c
 Traffic Server provides a sample script file named `example_alarm_bin.sh` in 
 the `bin` directory; simply modify the file to suit your needs.
 
-## Viewing Statistics from Traffic Line ## {#ViewingStatisticsfromTrafficLine}
+## Viewing Statistics from Traffic Line ## {#ViewingStatisticsTrafficLine}
 
 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](configure.htm#ConfiguringTrafficEdgeUsingTrafficLine) 
-and [Traffic Line Commands](cli.htm). You can view specific information about 
+information, refer to [Configuring Traffic Server Using Traffic Line](configure.htm#ConfiguringTSUsingTrafficLine) 
+and [Traffic Line Commands](../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. 
 
-##### To view a statistic: ##### {#viewastatistic}
+##### To view a statistic: ##### {#viewstatistic}
+
+Enter the following command:
 
-1. Log on to a Traffic Server node as the Traffic Server administrator; navigate to the Traffic Server `bin` directory.   
+        :::text
+        traffic_line -r variable
 
-2. Enter the following command:   
-`traffic_line -r _variable_`  
- where _`variable`_ is the variable representing the information you want to view. For a list of variables you can specify, refer to [Traffic Line Variables](cli.htm#1025718).   
+where _`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-commands##TrafficLineVariables).   
   
- For example, the following command displays the document hit rate for the Traffic Server node:   
-`traffic_line -r proxy.node.http.cache_hit_ratio`  
+For example, the following command displays the document hit rate for the Traffic Server node:
+
+     :::text
+     traffic_line -r proxy.node.http.cache_hit_ratio
   
- If the Traffic Server `bin` directory is not in your path, then prepend the Traffic Line command with `./` (for example: `./traffic_line -r _variable_`).
+If the Traffic Server `bin` directory is not in your path, then prepend the Traffic Line command
+with `./` (for example: `./traffic_line -r variable`).
+