Author: buildbot
Date: Sun May 15 00:54:43 2011
New Revision: 789600
Log:
Staging update by buildbot
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/getting-started/index.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/monitoring-traffic/index.en.html
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/getting-started/index.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/admin/getting-started/index.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/admin/getting-started/index.en.html
Sun May 15 00:54:43 2011
@@ -46,10 +46,10 @@ for <a href="https://cwiki.apache.org/co
<p>After you have installed Traffic Server on your system, you can do any of
the
following:</p>
<ul>
-<li><a href="#StartingTrafficEdge">Start Traffic Server</a></li>
-<li><a href="#StartingTrafficLine">Start Traffic Line</a></li>
-<li><a href="#StartingTrafficShell">Start Traffic Shell</a></li>
-<li><a href="#StoppingTrafficEdge">Stop Traffic Server</a></li>
+<li><a href="#StartTS">Start Traffic Server</a></li>
+<li><a href="#StartTrafficLine">Start Traffic Line</a></li>
+<li><a href="#StartTrafficShell">Start Traffic Shell</a></li>
+<li><a href="#StopTS">Stop Traffic Server</a></li>
</ul>
<h2 id="StartTS">Start Traffic Server</h2>
<p>To start Traffic Server manually, issue the <code>trafficserver</code>
command, passing
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/monitoring-traffic/index.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/admin/monitoring-traffic/index.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/admin/monitoring-traffic/index.en.html
Sun May 15 00:54:43 2011
@@ -44,7 +44,7 @@
analyzing network traffic.</p>
<p>This chapter discusses the following topics:</p>
<ul>
-<li><a href="#TrafficEdgeMonitoringTools">Traffic Server Monitoring
Tools</a></li>
+<li><a href="#TSMonitoringTools">Traffic Server Monitoring Tools</a></li>
<li><a href="#WorkingTrafficManagerAlarms">Working with Traffic Manager
Alarms</a></li>
<li><a href="#ViewingStatisticsTrafficLine">Viewing Statistics from Traffic
Line</a></li>
</ul>
@@ -52,11 +52,16 @@ analyzing network traffic.</p>
<p>Traffic Server provides the following tools to monitor system performance
and analyze network traffic:</p>
<ul>
-<li>Traffic Server can send email that's triggered by alarms that signal any
detected failure conditions; refer to <a
href="#WorkingTrafficManagerAlarms">Working with Traffic Manager
Alarms</a>.</li>
-<li>The Traffic Line command-line interface provides an alternative method of
viewing Traffic Server performance and network traffic information; refer to <a
href="#ViewingStatisticsTrafficLine">Viewing Statistics from Traffic
Line</a>.</li>
-<li>The Traffic Shell command-line tool provides yet another alternative
method of viewing Traffic Server performance and network traffic information;
refer to <a href="getstart.htm#StartingTrafficShell">Starting Traffic
Shell</a>.</li>
+<li>Traffic Server can send email that's triggered by alarms that signal any
+ detected failure conditions; refer to <a
href="#WorkingTrafficManagerAlarms">Working with Traffic Manager
Alarms</a>.</li>
+<li>The Traffic Line command-line interface provides an alternative method of
+ viewing Traffic Server performance and network traffic information;
+ refer to <a href="#ViewingStatisticsTrafficLine">Viewing Statistics from
Traffic Line</a>.</li>
+<li>The Traffic Shell command-line tool provides yet another alternative method
+ of viewing Traffic Server performance and network traffic information;
+ refer to <a href="../getting-started#StartTrafficShell">Starting Traffic
Shell</a>.</li>
</ul>
-<h2 id="WorkingwithTrafficManagerAlarms">Working with Traffic Manager
Alarms</h2>
+<h2 id="WorkingTrafficManagerAlarms">Working with Traffic Manager Alarms</h2>
<p>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.</p>
@@ -64,47 +69,40 @@ to write to a configuration file.</p>
<p>To configure Traffic Server to send an email to a specific address whenever
an alarm occurs, follow the steps below:</p>
<ol>
-<li>In a text editor, open the <code>records.config</code> file located in the
Traffic Server <code>config</code> directory.</li>
-<li>Set the <code>_proxy.config.alarm_email_</code> variable to the email
address alarms will be routed to.</li>
-<li>Save and close the <code>records.config</code> file.</li>
-<li>
-<p>Navigate to the Traffic Server <code>bin</code> directory. <br />
-</p>
-</li>
-<li>
-<p>Run the command <code>traffic_line -x</code> to apply the configuration
changes.</p>
-</li>
+<li>In the <a
href="../configuration-files/records.config"><code>records.config</code></a>
file</li>
+<li>Set the <a
href="../configuration-files/records.config#proxy.config.alarm_email"><em><code>proxy.config.alarm_email</code></em></a>
+ variable to the email address alarms will be routed to.</li>
+<li>Run the command <code>traffic_line -x</code> to apply the configuration
changes.</li>
</ol>
<h3 id="UsingaScriptFileforAlarms">Using a Script File for Alarms</h3>
<p>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
<code>example_alarm_bin.sh</code> in
the <code>bin</code> directory; simply modify the file to suit your needs.</p>
-<h2 id="ViewingStatisticsfromTrafficLine">Viewing Statistics from Traffic
Line</h2>
+<h2 id="ViewingStatisticsTrafficLine">Viewing Statistics from Traffic Line</h2>
<p>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 <a
href="configure.htm#ConfiguringTrafficEdgeUsingTrafficLine">Configuring Traffic
Server Using Traffic Line</a>
-and <a href="cli.htm">Traffic Line Commands</a>. You can view specific
information about
+information, refer to <a
href="configure.htm#ConfiguringTSUsingTrafficLine">Configuring Traffic Server
Using Traffic Line</a>
+and <a href="../traffic-line-commands">Traffic Line Commands</a>. 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. </p>
-<h5 id="viewastatistic">To view a statistic:</h5>
-<ol>
-<li>
-<p>Log on to a Traffic Server node as the Traffic Server administrator;
navigate to the Traffic Server <code>bin</code> directory. <br />
-</p>
-</li>
-<li>
-<p>Enter the following command: <br />
-<code>traffic_line -r _variable_</code><br />
- where <em><code>variable</code></em> is the variable representing the
information you want to view. For a list of variables you can specify, refer to
<a href="cli.htm#1025718">Traffic Line Variables</a>. <br />
-</p>
-</li>
-</ol>
-<p>For example, the following command displays the document hit rate for the
Traffic Server node: <br />
-<code>traffic_line -r proxy.node.http.cache_hit_ratio</code><br />
+<h5 id="viewstatistic">To view a statistic:</h5>
+<p>Enter the following command:</p>
+<div class="codehilite"><pre> traffic_line -r variable
+</pre></div>
+
+
+<p>where <em><code>variable</code></em> is the variable representing the
information you want to view.
+For a list of variables you can specify, refer to <a
href="../traffic-line-commands##TrafficLineVariables">Traffic Line
Variables</a>. <br />
</p>
-<p>If the Traffic Server <code>bin</code> directory is not in your path, then
prepend the Traffic Line command with <code>./</code> (for example:
<code>./traffic_line -r _variable_</code>).</p>
+<p>For example, the following command displays the document hit rate for the
Traffic Server node:</p>
+<div class="codehilite"><pre> traffic_line -r proxy.node.http.cache_hit_ratio
+</pre></div>
+
+
+<p>If the Traffic Server <code>bin</code> directory is not in your path, then
prepend the Traffic Line command
+with <code>./</code> (for example: <code>./traffic_line -r
variable</code>).</p>
</div>
</div><!-- main -->
