A note about per-module logging.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1001245 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 28 insertions, 0 deletions

diff --git a/docs/manual/logs.xml b/docs/manual/logs.xml
index dd44199c7b..4ac8a6008f 100644
--- a/docs/manual/logs.xml
+++ b/docs/manual/logs.xml
@@ -158,6 +158,34 @@
     </example>
   </section>
 
+  <section id="permodule">
+    <title>Per-module logging</title>
+
+    <p>The <directive module="core">LogLevel</directive> directive
+    allows you to specify a log severity level on a per-module basis. In
+    this way, if you are troubleshooting a problem with just one
+    particular module, you can turn up its logging volume without also
+    getting the details of other modules that you're not interested in.
+    This is particularly useful for modules such as
+    <module>mod_proxy</module> or <module>mod_rewrite</module> where you
+    want to know details about what it's trying to do.</p>
+
+    <p>Do this by specifying the name of the module in your
+    <directive>LogLevel</directive> directive:</p>
+
+    <example>
+    LogLevel info rewrite:trace5
+    </example>
+
+    <p>This sets the main <directive>LogLevel</directive> to info, but
+    turns it up to <code>trace5</code> for
+    <module>mod_rewrite</module>.</p>
+
+    <note>This replaces the per-module logging directives, such as
+    <code>RewriteLog</code>, that were present in earlier versions of
+    the server.</note>
+  </section>
+
   <section id="accesslog">
     <title>Access Log</title>