You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2013/10/07 17:40:52 UTC
svn commit: r881572 - in /websites/staging/sling/trunk/content: ./
documentation/development/ site/
Author: buildbot
Date: Mon Oct 7 15:40:52 2013
New Revision: 881572
Log:
Staging update by buildbot for sling
Removed:
websites/staging/sling/trunk/content/site/bundle-resources-extensionsbundleresource.html
websites/staging/sling/trunk/content/site/logging.html
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/client-request-logging.html
websites/staging/sling/trunk/content/documentation/development/logging.html
websites/staging/sling/trunk/content/site/.htaccess
websites/staging/sling/trunk/content/sitemap.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Oct 7 15:40:52 2013
@@ -1 +1 @@
-1529902
+1529977
Modified: websites/staging/sling/trunk/content/documentation/development/client-request-logging.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/client-request-logging.html (original)
+++ websites/staging/sling/trunk/content/documentation/development/client-request-logging.html Mon Oct 7 15:40:52 2013
@@ -83,11 +83,6 @@
</div>
- <div class="tip">
- This page is a translated version of <a href="/site/client-request-logging.html" target="sling_cwiki">/site/client-request-logging.html</a>. In case of
- doubt you might want to refer to the old page.
- </div>
-
<h1>Client Request Logging</h1>
<p>Sling provides extensive support to log various information at the before and after processing client requests. Out of the box, there are two loggers configured to write traditional <code>access.log</code> and <code>request.log</code> files. In addition more logging can be configured by providing OSGi Configuration Admin configuration.</p>
@@ -107,7 +102,7 @@
<tr>
<td>Request Log Name</td>
<td><code>request.log.output</code></td>
-<td>Name of the destination for the request log. The request log logs the entry and exit of each request into and out of the system together with the entry time, exit time, time to process the request, a request counter as well as the final status code and response content type. In terms of Request Logger Service formats, request entry is logged with the format <code>%t \[%R\] \-> %m %U%q %H</code> and request exit is logged with the format <code>%\{end}t \[%R] <\- %s %\{Content-Type}o %Dms</code> (See [#Log Format Specification] below for the specification of the format).</td>
+<td>Name of the destination for the request log. The request log logs the entry and exit of each request into and out of the system together with the entry time, exit time, time to process the request, a request counter as well as the final status code and response content type. In terms of Request Logger Service formats, request entry is logged with the format <code>%t \[%R\] \-> %m %U%q %H</code> and request exit is logged with the format <code>%\{end}t \[%R] <\- %s %\{Content-Type}o %Dms</code> (See <a href="#log-format-specification">Log Format Specification</a> below for the specification of the format).</td>
<td></td>
</tr>
<tr>
@@ -170,7 +165,7 @@
</tr>
</tbody>
</table>
-<p><em>Note:</em> If logging to a file, this file is not rotated and/or limited by size. To get log file rotation use the <em>Logger Name</em> logging type. See <a href="#rotating-logger-files">#Rotating Logger Files</a> below for information on how logging information can be written to rotated and/or size limited files.</p>
+<p><em>Note:</em> If logging to a file, this file is not rotated and/or limited by size. To get log file rotation use the <em>Logger Name</em> logging type. See <a href="#rotating-logger-files">Rotating Logger Files</a> below for information on how logging information can be written to rotated and/or size limited files.</p>
<h3 id="additional-per-request-loggers">Additional per-request Loggers</h3>
<p>In the Web Console create <em>Apache Sling Customizable Request Data Logger</em> (Factory PID=<code>org.apache.sling.engine.impl.log.RequestLoggerService</code>) configuration.</p>
<p>In the Sling Web Console locate the Configuration page (<code>/system/console/configMgr</code>) and click on the <code>+</code> (plus) symbol on the <em>Apache Sling Customizable Request Data Logger</em> line. This opens a dialog to enter the configuration whose properties can be configured as follows:</p>
@@ -187,20 +182,20 @@
<tr>
<td>Log Format</td>
<td><code>request.log.service.format</code></td>
-<td>Specify a <a href="#log-format-specification">#Log Format Specification</a> as described below</td>
-<td></td>
+<td> </td>
+<td>Specify a <a href="#log-format-specification">Log Format Specification</a> as described below</td>
</tr>
<tr>
<td>Logger Type</td>
<td><code>request.log.service.outputtype</code></td>
<td>Logger Name/<code>0</code></td>
-<td>Type of Logger named with the Logger Name parameter. See <a href="#log-output">#Log Output</a> above</td>
+<td>Type of Logger named with the Logger Name parameter. See <a href="#log-output">Log Output</a> above</td>
</tr>
<tr>
<td>Logger Name</td>
<td><code>request.log.service.output</code></td>
<td><code>request.log</code></td>
-<td>Name of the Logger to be used. See <a href="#log-output">#Log Output</a> above</td>
+<td>Name of the Logger to be used. See <a href="#log-output">Log Output</a> above</td>
</tr>
<tr>
<td>Request Entry</td>
@@ -299,7 +294,7 @@
</tr>
<tr>
<td><code>%P</code></td>
-<td>The <em>name of the thread</em> -process ID of the child- that serviced the request.</td>
+<td>The <em>name of the thread</em> ~~process ID of the child~~ that serviced the request.</td>
</tr>
<tr>
<td><code>%\{format}P</code></td>
@@ -372,15 +367,17 @@
<p>If you want to write the request (and access) logging information into a rotated file, you should configure as follows:</p>
<ol>
<li>Configure the Log Type to be a <em>Logger Name</em> and some usefull Logger name. For example <code>clientlog.request</code>.</li>
-<li>Create an <em>Apache Sling Logging Logger Configuration</em> for this Logger name according to <a href="">Logging Configuration</a> with the following setup:
- <strong> Allow message at INFO (Information) level to be logged which is the level used by the request loggers
- </strong> Define the appropriate log file name, for example <code>logs/client.request.log</code>
- <strong> Use only <code>\{5</code>} as the message format because request logger messages are generally already fully formated with required timestamp etc.
- </strong> Add any Logger names used for the client request log configuration, <code>clientlog.request</code> in the example above, to the Logger field. By clicking on the <code>+</code> (plus) button you may add more than a single logger name whose messages are written to this file.</li>
+<li>Create an <em>Apache Sling Logging Logger Configuration</em> for this Logger name according to <a href="">Logging Configuration</a> with the following setup:<ul>
+<li>Allow message at INFO (Information) level to be logged which is the level used by the request loggers</li>
+<li>Define the appropriate log file name, for example <code>logs/client.request.log</code></li>
+<li>Use only <code>\{5</code>} as the message format because request logger messages are generally already fully formated with required timestamp etc.</li>
+<li>Add any Logger names used for the client request log configuration, <code>clientlog.request</code> in the example above, to the Logger field. By clicking on the <code>+</code> (plus) button you may add more than a single logger name whose messages are written to this file.</li>
+</ul>
+</li>
<li>Optionally, you may create an <em>Apache Sling Logging Writer Configuration</em> for the log file defined in the previous step to better control rotation setup. See <a href="">Log Writer Configuration</a> for full details.</li>
</ol>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1499238 by fmeschbe on Wed, 3 Jul 2013 07:39:54 +0000
+ Rev. 1529977 by dklco on Mon, 7 Oct 2013 15:40:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/documentation/development/logging.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/logging.html (original)
+++ websites/staging/sling/trunk/content/documentation/development/logging.html Mon Oct 7 15:40:52 2013
@@ -83,11 +83,6 @@
</div>
- <div class="tip">
- This page is a translated version of <a href="/site/logging.html" target="sling_cwiki">/site/logging.html</a>. In case of
- doubt you might want to refer to the old page.
- </div>
-
<h1>Logging</h1>
<h2 id="introduction">Introduction</h2>
@@ -272,7 +267,7 @@
<p>Log file rotation by size is specified by setting the <code>org.apache.sling.commons.log.file.size</code> property to a plain number or a number plus a size multiplier. The size multiplier may be any of <code>K</code>, <code>KB</code>, <code>M</code>, <code>MB</code>, <code>G</code>, or <code>GB</code> where the case is ignored and the meaning is probably obvious.</p>
<p>When using Size Rotation, the <code>org.apache.sling.commons.log.file.number</code> defines the number of old log file generations to keep. For example to keep 5 old log files indexed by 0 through 4, set the <code>org.apache.sling.commons.log.file.number</code> to <code>5</code> (which happens to be the default).</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1499238 by fmeschbe on Wed, 3 Jul 2013 07:39:54 +0000
+ Rev. 1529977 by dklco on Mon, 7 Oct 2013 15:40:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/site/.htaccess
==============================================================================
--- websites/staging/sling/trunk/content/site/.htaccess (original)
+++ websites/staging/sling/trunk/content/site/.htaccess Mon Oct 7 15:40:52 2013
@@ -57,3 +57,5 @@ Redirect Permanent /site/wrap-or-decorat
Redirect Permanent /site/xslt-processing-pipeline.html /old-stuff/scriptengineintegration/xslt-processing-pipeline.html
Redirect Permanent /site/commons-html-utilities.html /documentation/bundles/commons-html-utilities.html
Redirect Permanent /site/manipulating-content-the-slingpostservlet-servletspost.html /documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html
+Redirect Permanent /site/logging.html /documentation/development/logging.html
+Redirect Permanent /site/bundle-resources-extensionsbundleresource.html /documentation/bundles/bundle-resources-extensions-bundleresource.html#configuration
Modified: websites/staging/sling/trunk/content/sitemap.html
==============================================================================
--- websites/staging/sling/trunk/content/sitemap.html (original)
+++ websites/staging/sling/trunk/content/sitemap.html Mon Oct 7 15:40:52 2013
@@ -106,7 +106,7 @@
<li><a href="/documentation/bundles/output-rewriting-pipelines-org-apache-sling-rewriter.html">Output Rewriting Pipelines (org.apache.sling.rewriter)</a></li>
<li><a href="/documentation/bundles/request-analysis.html">Request Processing Analyzer (reqanalyzer)</a></li>
<li><a href="/documentation/bundles/scheduler-service-commons-scheduler.html">Scheduler Service (commons scheduler)</a></li>
-<li><a href="/documentation/bundles/sling-health-check-tool.html">Sling Health Check Tool</a></li>
+<li><a href="/documentation/bundles/sling-health-check-tool.html">Sling Health Check Tools</a></li>
<li><a href="/documentation/bundles/sling-scripting-jsp-taglib.html">Sling Scripting JSP Taglib</a></li>
<li><a href="/documentation/bundles/sling-settings-org-apache-sling-settings.html">Sling Settings (org.apache.sling.settings)</a></li>
<li><a href="/documentation/bundles/web-console-extensions.html">Web Console Extensions</a></li>