svn commit: r1394355 - /trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext

[jp...@apache.org]

Author: jpeach
Date: Fri Oct  5 03:55:49 2012
New Revision: 1394355

URL: http://svn.apache.org/viewvc?rev=1394355&view=rev
Log:
Document proxy.config.diags.output.*

Modified:
    trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext

Modified: trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext?rev=1394355&r1=1394354&r2=1394355&view=diff
==============================================================================
--- trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext (original)
+++ trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext Fri Oct  5 03:55:49 2012
@@ -1017,7 +1017,7 @@ the `records.config` file.
 :   When disabled (`0`), Traffic Server always uses the same origin server for the same client, for as long as the origin server is available.
 
 
-# Logging Config # {#LoggingConfig}
+# Logging Configuration # {#LoggingConfig}
 
 *`proxy.config.log.logging_enabled`* {#proxy.config.log.logging_enabled}
 :   `INT`
@@ -1275,6 +1275,29 @@ the `records.config` file.
 :   Default: `0`
 :   The number of milliseconds before a slow connection's debugging stats are dumped. Specify `1` to enable or `0` to disable.
 
+# Diagnostic Logging Configuration # {#DiagnosticLogging}
+
+*`proxy.config.diags.output.diag`* {proxy.config.diags.output.diag}
+*`proxy.config.diags.output.debug`* {proxy.config.diags.output.debug}
+*`proxy.config.diags.output.status`* {proxy.config.diags.output.status}
+*`proxy.config.diags.output.note`* {proxy.config.diags.output.note}
+*`proxy.config.diags.output.warning`* {proxy.config.diags.output.warning}
+*`proxy.config.diags.output.error`* {proxy.config.diags.output.error}
+*`proxy.config.diags.output.fatal`* {proxy.config.diags.output.fatal}
+*`proxy.config.diags.output.alert`* {proxy.config.diags.output.alert}
+*`proxy.config.diags.output.emergency`* {proxy.config.diags.output.emergency}
+:   `STRING`
+:   These options control where Traffic Server should log diagnostic output.  Messages at diagnostic level can be directed to any combination of diagnostic destinations. Valid diagnostic message destinations are:
+
+    * 'O' = Log to standard output
+    * 'E' = Log to standard error
+    * 'S' = Log to syslog
+    * 'L' = Log to diags.log
+
+    For example, to log debug messages to syslog and diags.log:
+
+        proxy.config.diags.output.debug STRING SL
+
 
 # Reverse Proxy # {#ReverseProxy}