svn commit: r857838 - in /websites/staging/trafficserver/trunk: cgi-bin/ content/ content/docs/trunk/sdk/troubleshooting-tips/unable-to-debug-tags.en.html

[bu...@apache.org]

Author: buildbot
Date: Tue Apr  9 04:42:35 2013
New Revision: 857838

Log:
Staging update by buildbot for trafficserver

Modified:
    websites/staging/trafficserver/trunk/cgi-bin/   (props changed)
    websites/staging/trafficserver/trunk/content/   (props changed)
    websites/staging/trafficserver/trunk/content/docs/trunk/sdk/troubleshooting-tips/unable-to-debug-tags.en.html

Propchange: websites/staging/trafficserver/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr  9 04:42:35 2013
@@ -1 +1 @@
-1465694
+1465881

Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr  9 04:42:35 2013
@@ -1 +1 @@
-1465694
+1465881

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/troubleshooting-tips/unable-to-debug-tags.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/troubleshooting-tips/unable-to-debug-tags.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/troubleshooting-tips/unable-to-debug-tags.en.html Tue Apr  9 04:42:35 2013
@@ -66,7 +66,7 @@ to add traces in your plugin. In this AP
 out <em><code>format_str</code></em></p>
 </li>
 <li>
-<p><code>...</code> is a variable for <em><code>format_str</code></em></p>
+<p><code>...</code> are variables for <em><code>format_str</code></em> in the standard <code>printf</code> style.</p>
 </li>
 </ul>
 <p>Run Traffic Server with the <code>-Ttag</code> option. For example, if the tag is
@@ -95,14 +95,49 @@ Server with the <code>my-plugin</code> t
 
 
 <h3 id="OtherUsefulInternalDebugTags">Other Useful Internal Debug Tags</h3>
-<p>Traffic Server provides many debug tags for internal debugging purposes. Some 
+<p>Embedded in the base Traffic Server code are many debug tags for internal debugging purposes. These can also be used to follow Traffic Server behavior for testing and analysis.</p>
+<p>The debug tag setting (<code>-T</code> and <code>proxy.config.diag.debug.tags</code>) is a anchored regular expression against which the tag for a specific debug message is matched. This means the value "http" matches debug emssages with the tag "http" but also "http_seq" and "http_trans". If you want multiple tags then use a pipe symbol to separate the tags. For example "http_tproxy|dns|hostdb" will match any of the message tags "http_tproxy", "dns", "hostdb", or "dns_srv" (but not "http_trans" nor "splitdns").</p>
+<p>Some 
 of the useful HTTP debug tags are:</p>
 <ul>
 <li>
 <p><code>http_hdrs</code> - traces all incoming and outgoing HTTP headers.</p>
 </li>
 <li>
-<p><code>http.*</code> - traces all the STTP SM debug statements.</p>
+<p><code>http_trans</code> - traces actions in an HTTP transaction.</p>
+</li>
+<li>
+<p><code>http_seq</code> - traces the sequence of the HTTP state machine.</p>
+</li>
+<li>
+<p><code>http_tproxy</code> - transparency related HTTP events</p>
+</li>
+<li>
+<p><code>dns</code> - DNS operations</p>
+</li>
+<li>
+<p><code>hostdb</code> - Host name lookup</p>
+</li>
+<li>
+<p><code>iocore_net</code> - Socket and low level IO (very voluminous)</p>
+</li>
+<li>
+<p><code>socket</code> - socket operations</p>
+</li>
+<li>
+<p><code>ssl</code> - SSL related events</p>
+</li>
+<li>
+<p><code>cache</code> - Cache operations (many subtags, examine the output to narrow the tag set)</p>
+</li>
+<li>
+<p><code>cache_update</code> - Cache updates including writes</p>
+</li>
+<li>
+<p><code>cache_read</code> - Cache read events.</p>
+</li>
+<li>
+<p><code>dir_probe</code> - Cache searches.</p>
 </li>
 <li>
 <p><code>sdk</code> - gives some warning concerning API usage.</p>