Author: buildbot
Date: Mon Jul 27 10:08:39 2015
New Revision: 959745
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/logging.html
websites/staging/sling/trunk/content/documentation/development/sling-log-support.png
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 27 10:08:39 2015
@@ -1 +1 @@
-1692724
+1692853
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 Jul 27 10:08:39 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><strong><a href="/documentation.html">Documentation</a></strong> <br
/>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><strong><a href="/documentation.html">Documentation</a></strong> <br />
<a href="/documentation/getting-started.html">Getting Started</a> <br />
<a href="/documentation/the-sling-engine.html">The Sling Engine</a> <br />
<a href="/documentation/development.html">Development</a> <br />
@@ -90,7 +101,18 @@
<h1>Logging</h1>
- <div class="note">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<div class="note">
This document is for the new (November 2013) 4.x release of the Sling Commons
Log components. Refer to
<a href="http://sling.apache.org/documentation/legacy/logging.html";>Logging
3.x</a> for older versions.
</div>
@@ -98,6 +120,7 @@ This document is for the new (November 2
<div class="toc">
<ul>
<li><a href="#introduction">Introduction</a></li>
+<li><a href="#webconsole-plugin">WebConsole Plugin</a></li>
<li><a href="#initial-configuration">Initial Configuration</a></li>
<li><a href="#user-configuration-osgi-based">User Configuration - OSGi
Based</a><ul>
<li><a href="#logger-configuration">Logger Configuration</a></li>
@@ -122,7 +145,7 @@ This document is for the new (November 2
</li>
<li><a href="#external-config-file">External Config File</a></li>
<li><a href="#java-util-logging-jul-integration">Java Util Logging (JUL)
Integration</a></li>
-<li><a
href="#wzxhzdk16wzxhzdk17configuring-osgi-appenders-in-the-logback-config"><a
name="config-override"></a>Configuring OSGi appenders in the Logback
Config</a></li>
+<li><a href="#configuring-osgi-appenders-in-the-logback-config"><a
name="config-override"></a>Configuring OSGi appenders in the Logback
Config</a></li>
</ul>
</li>
<li><a href="#using-slf4j-api-17">Using Slf4j API 1.7</a></li>
@@ -140,10 +163,9 @@ This document is for the new (November 2
<li><a href="#q-how-to-start-sling-with-an-external-logbackxml-file">Q. How to
start Sling with an external logback.xml file</a></li>
</ul>
</li>
-<li><a href="#webconsole-plugin">WebConsole Plugin</a></li>
</ul>
</div>
-<h2 id="introduction">Introduction</h2>
+<h2 id="introduction">Introduction<a class="headerlink" href="#introduction"
title="Permanent link">¶</a></h2>
<p>Logging in Sling is supported by the
<code>org.apache.sling.commons.log</code> bundle, which is one of the first
bundles installed
and started by the Sling Launcher. This bundle along with other bundles
manages the Sling Logging and provides the
following features:</p>
@@ -157,9 +179,22 @@ following features:</p>
<li>Configures logging through Logback which is integrated with the OSGi
environment</li>
<li>Allows logging to be configured both via editing Logback xml or via OSGi
Configurations</li>
</ul>
-<h2 id="initial-configuration">Initial Configuration</h2>
+<h2 id="webconsole-plugin">WebConsole Plugin<a class="headerlink"
href="#webconsole-plugin" title="Permanent link">¶</a></h2>
+<p>The Web Console Plugin supports the following features:</p>
+<ul>
+<li>Display the list of loggers which have levels or appenders configured.</li>
+<li>List the file appenders with the location of current active log files.</li>
+<li>Show the contents of LogBack config files.</li>
+<li>Show the contents of various Logback config fragments.</li>
+<li>Show Logback Status logs.</li>
+<li>Inline edit the Logger setting</li>
+<li>Configure Logger with content assist for logger names</li>
+<li>Provides links to log file content allows log file content to be viewed
from Web UI</li>
+</ul>
+<p><img src="sling-log-support.png" /></p>
+<h2 id="initial-configuration">Initial Configuration<a class="headerlink"
href="#initial-configuration" title="Permanent link">¶</a></h2>
<p>The <code>org.apache.sling.commons.log</code> bundle gets its initial
configuration from the following <code>BundleContext</code> properties:</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Property</th>
@@ -208,18 +243,28 @@ following features:</p>
<td>true</td>
<td>Boolean property to control packaging data support of Logback. See <a
href="http://www.slf4j.org/manual.html#mdc";>Packaging Data</a> section of
Logback for more details</td>
</tr>
+<tr>
+<td><code>org.apache.sling.commons.log.numOfLines</code></td>
+<td>1000</td>
+<td>Number of lines from each log files to include while generating the dump
in 'txt' mode. If set to -1 then whole file would be included</td>
+</tr>
+<tr>
+<td><code>org.apache.sling.commons.log.maxOldFileCountInDump</code></td>
+<td>3</td>
+<td>Maximum number of old rolled over files for each active file to be
included while generating the dump as part of Status zip support</td>
+</tr>
</tbody>
</table>
-<h2 id="user-configuration-osgi-based">User Configuration - OSGi Based</h2>
+<h2 id="user-configuration-osgi-based">User Configuration - OSGi Based<a
class="headerlink" href="#user-configuration-osgi-based" title="Permanent
link">¶</a></h2>
<p>User Configuration after initial configuration is provided by the
Configuration Admin Service. To this avail two
<code>org.osgi.services.cm.ManagedServiceFactory</code> services are
registered under the PIDs
<code>org.apache.sling.commons.log.LogManager.factory.writer</code>
and <code>org.apache.sling.commons.log.LogManager.factory.config</code> to
receive configurations.</p>
-<h3 id="logger-configuration">Logger Configuration</h3>
+<h3 id="logger-configuration">Logger Configuration<a class="headerlink"
href="#logger-configuration" title="Permanent link">¶</a></h3>
<p>Loggers (or Categories) can be configured to log to specific files at
specific levels using configurable patterns.
To this avail factory configuration instances with factory PID
<code>org.apache.sling.commons.log.LogManager.factory.config</code>
may be created and configured with the Configuration Admin Service.</p>
<p>The following properties may be set:</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Property</th>
@@ -253,15 +298,21 @@ may be created and configured with the C
<td>--</td>
<td>A list of logger names to which this configuration applies.</td>
</tr>
+<tr>
+<td><code>org.apache.sling.commons.log.additiv</code></td>
+<td><code>Boolean</code></td>
+<td>false</td>
+<td>If set to false then logs from these loggers would not be sent to any
appender attached higher in the hierarchy</td>
+</tr>
</tbody>
</table>
<p>Note that multiple Logger Configurations may refer to the same Log Writer
Configuration. If no Log Writer Configuration
exists whose file name matches the file name set on the Logger Configuration
an implicit Log Writer Configuration
with default setup (daily log rotation) is internally created.</p>
-<h3 id="log-writer-configuration">Log Writer Configuration</h3>
+<h3 id="log-writer-configuration">Log Writer Configuration<a
class="headerlink" href="#log-writer-configuration" title="Permanent
link">¶</a></h3>
<p>Log Writer Configuration is used to setup file output and log file rotation
characteristics for log writers used by the Loggers.</p>
<p>The following properties may be set:</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Property</th>
@@ -289,14 +340,14 @@ with default setup (daily log rotation)
</table>
<p>See the section <em>Log File Rotation</em> below for full details on the
<code>org.apache.sling.commons.log.file.size</code> and
<code>org.apache.sling.commons.log.file.number</code> properties.</p>
-<h4 id="log-file-rotation">Log File Rotation</h4>
+<h4 id="log-file-rotation">Log File Rotation<a class="headerlink"
href="#log-file-rotation" title="Permanent link">¶</a></h4>
<p>Log files can grow rather quickly and fill up available disk space. To cope
with this growth log files may be rotated in
two ways: At specific times or when the log file reaches a configurable size.
The first method is called <em>Scheduled Rotation</em>
and is used by specifying a <code>SimpleDateFormat</code> pattern as the log
file "size". The second method is called <em>Size Rotation</em>
and is used by setting a maximum file size as the log file size.</p>
<p>As of version 2.0.6 of the Sling Commons Log bundle, the default value for
log file scheduling is <code>'.'yyyy-MM-dd</code>
causing daily log rotation. In previous version, log rotation defaults to a
10MB file size limit.</p>
-<h5 id="scheduled-rotation">Scheduled Rotation</h5>
+<h5 id="scheduled-rotation">Scheduled Rotation<a class="headerlink"
href="#scheduled-rotation" title="Permanent link">¶</a></h5>
<p>The rolling schedule is specified by setting the
<code>org.apache.sling.commons.log.file.size</code> property to a
<code>java.text.SimpleDateFormat</code> pattern. Literal text (such as a
leading dot) to be included must be <em>enclosed</em> within a
pair of single quotes. A formatted version of the date pattern is used as the
suffix for the rolled file name. Internally
@@ -306,7 +357,7 @@ more details around the pattern format</
2001-02-16 at midnight, the logging file <code>/foo/bar.log</code> will be
renamed to <code>/foo/bar.log.2001-02-16</code> and logging for
2001-02-17 will continue in a new <code>/foo/bar.log</code> file until it
rolls over the next day.</p>
<p>It is possible to specify monthly, weekly, half-daily, daily, hourly, or
minutely rollover schedules.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>DatePattern</th>
@@ -351,14 +402,14 @@ more details around the pattern format</
protocol specification of a URL which is probably not what you want.</p>
<p>Note that Scheduled Rotation ignores the
<code>org.apache.sling.commons.log.file.number</code> property since the old
log files are
not numbered but "dated".</p>
-<h5 id="size-rotation">Size Rotation</h5>
+<h5 id="size-rotation">Size Rotation<a class="headerlink"
href="#size-rotation" title="Permanent link">¶</a></h5>
<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>
-<h2 id="logback-integration">Logback Integration</h2>
+<h2 id="logback-integration">Logback Integration<a class="headerlink"
href="#logback-integration" title="Permanent link">¶</a></h2>
<p>Logback integration provides following features</p>
<ul>
<li>LogBack configuration can be provided via Logback config xml</li>
@@ -369,7 +420,7 @@ to <code>5</code> (which happens to be t
<li>Exposes Logback runtime state through the Felix WebConsole Plugin</li>
</ul>
<p>The following sections provide more details.</p>
-<h3 id="turbofilters-as-osgi-services">TurboFilters as OSGi Services</h3>
+<h3 id="turbofilters-as-osgi-services">TurboFilters as OSGi Services<a
class="headerlink" href="#turbofilters-as-osgi-services" title="Permanent
link">¶</a></h3>
<p><a href="http://logback.qos.ch/manual/filters.html#TurboFilter";>Logback
TurboFilters</a> operate globally and are invoked for every Logback call. To
register an OSGi <code>TurboFilter</code>,
just to register an service that implements the
<code>ch.qos.logback.classic.turbo.TurboFilter</code> interface.</p>
<div class="codehilite"><pre><span class="kn">import</span> <span
class="nn">import</span> <span class="n">ch</span><span class="o">.</span><span
class="na">qos</span><span class="o">.</span><span
class="na">logback</span><span class="o">.</span><span
class="na">classic</span><span class="o">.</span><span
class="na">turbo</span><span class="o">.</span><span
class="na">MatchingFilter</span><span class="o">;</span>
@@ -391,7 +442,7 @@ just to register an service that impleme
<p>As these filters are invoked for every call they must execute quickly.</p>
-<h3 id="filters-as-osgi-services">Filters as OSGi services</h3>
+<h3 id="filters-as-osgi-services">Filters as OSGi services<a
class="headerlink" href="#filters-as-osgi-services" title="Permanent
link">¶</a></h3>
<p><a href="http://logback.qos.ch/manual/filters.html";>Logback Filters</a> are
attached to appenders and are used to determine if any LoggingEvent needs to
be passed to the appender. When registering a filter the bundle needs to
configure a service property
<code>appenders</code> which refers to list of appender names to which the
Filter must be attached</p>
@@ -415,7 +466,8 @@ be passed to the appender. When register
</pre></div>
-<h3 id="appenders-as-osgi-services">Appenders as OSGi services</h3>
+<p>If the <code>appenders</code> value is set to <code>*</code> then the
filter would be registered with all the appenders (<code>Since 4.0.4</code>)</p>
+<h3 id="appenders-as-osgi-services">Appenders as OSGi services<a
class="headerlink" href="#appenders-as-osgi-services" title="Permanent
link">¶</a></h3>
<p><a href="http://logback.qos.ch/manual/appenders.html";>Logback Appenders</a>
handle the logging events produced by Logback. To register an OSGi
<code>Appender</code>,
just register a service that implements the
<code>ch.qos.logback.core.Appender</code> interface. Such a service must
have a <code>loggers</code> service property, which refers to list of logger
names to which the Appender must be attached.</p>
@@ -431,11 +483,11 @@ have a <code>loggers</code> service prop
</pre></div>
-<h3 id="logback-config-fragment-support">Logback Config Fragment Support</h3>
+<h3 id="logback-config-fragment-support">Logback Config Fragment Support<a
class="headerlink" href="#logback-config-fragment-support" title="Permanent
link">¶</a></h3>
<p>Logback supports including parts of a configuration file from another file
(See <a
href="http://logback.qos.ch/manual/configuration.html#fileInclusion";>File
Inclusion</a>). This module
extends that support by allowing other bundles to provide config fragments.
There are two ways to achieve that,
described below.</p>
-<h4 id="logback-config-fragments-as-string-objects">Logback config fragments
as String objects</h4>
+<h4 id="logback-config-fragments-as-string-objects">Logback config fragments
as String objects<a class="headerlink"
href="#logback-config-fragments-as-string-objects" title="Permanent
link">¶</a></h4>
<p>If you have the config as string then you can register that String instance
as a service with property <code>logbackConfig</code>
set to true. The Sling Logback Extension monitors such objects and passes them
to logback.</p>
<div class="codehilite"><pre><span class="n">Properties</span> <span
class="n">props</span> <span class="o">=</span> <span class="k">new</span>
<span class="n">Properties</span><span class="o">();</span>
@@ -460,7 +512,7 @@ set to true. The Sling Logback Extension
<p>If the config needs to be updated just re-register the service so that
changes are picked up.</p>
-<h4 id="logback-config-fragments-as-configprovider-instances">Logback config
fragments as ConfigProvider instances</h4>
+<h4 id="logback-config-fragments-as-configprovider-instances">Logback config
fragments as ConfigProvider instances<a class="headerlink"
href="#logback-config-fragments-as-configprovider-instances" title="Permanent
link">¶</a></h4>
<p>Another way to provide config fragments is with services that implement the
<code>org.apache.sling.commons.log.logback.ConfigProvider</code> interface.</p>
<div class="codehilite"><pre><span class="nd">@Component</span>
@@ -479,7 +531,7 @@ resets the Logback runtime.</p>
</pre></div>
-<h3 id="external-config-file">External Config File</h3>
+<h3 id="external-config-file">External Config File<a class="headerlink"
href="#external-config-file" title="Permanent link">¶</a></h3>
<p>Logback can be configured with an external file. The file name can be
specified through</p>
<ol>
<li>OSGi config - Look for a config with name <code>Apache Sling Logging
Configuration</code> and specify the config file path.</li>
@@ -496,7 +548,7 @@ action entry:</p>
<p>The <code>osgi</code> element enables the OSGi integration support</p>
-<h3 id="java-util-logging-jul-integration">Java Util Logging (JUL)
Integration</h3>
+<h3 id="java-util-logging-jul-integration">Java Util Logging (JUL)
Integration<a class="headerlink" href="#java-util-logging-jul-integration"
title="Permanent link">¶</a></h3>
<p>The bundle also support <a
href="http://www.slf4j.org/api/org/slf4j/bridge/SLF4JBridgeHandler.html";>SLF4JBridgeHandler</a>.
The two steps listed below enable the JUL integration.
This allows for routing logging messages from JUL to the Logbback
appenders.</p>
<ol>
@@ -504,7 +556,7 @@ This allows for routing logging messages
</ol>
<p>If <code>org.apache.sling.commons.log.julenabled</code> is found to be true
then <a
href="http://logback.qos.ch/manual/configuration.html#LevelChangePropagator";>LevelChangePropagator</a>
would be
registered automatically with Logback </p>
-<h3 id="wzxhzdk16wzxhzdk17configuring-osgi-appenders-in-the-logback-config"><a
name="config-override"></a>Configuring OSGi appenders in the Logback Config</h3>
+<h3 id="configuring-osgi-appenders-in-the-logback-config"><a
name="config-override"></a>Configuring OSGi appenders in the Logback Config<a
class="headerlink" href="#configuring-osgi-appenders-in-the-logback-config"
title="Permanent link">¶</a></h3>
<p>So far Sling used to configure the appenders based on OSGi config. This
provides a very limited
set of configuration options. To make use of other Logback features you can
override the OSGi config
from within the Logback config file. OSGi config based appenders are named
based on the file name.</p>
@@ -531,7 +583,7 @@ create an appender with the name <code>l
<p>In this case the logging module creates an appender based on the Logback
config instead of the OSGi config.
This can be used to move the application from OSGi based configs to Logback
based configs.</p>
-<h2 id="using-slf4j-api-17">Using Slf4j API 1.7</h2>
+<h2 id="using-slf4j-api-17">Using Slf4j API 1.7<a class="headerlink"
href="#using-slf4j-api-17" title="Permanent link">¶</a></h2>
<p>With Slf4j API 1.7 onwards its possible to use logger methods with varargs
i.e. log n arguments without
constructing an object array e.g. <code>log.info("This is a test {} , {}, {},
{}",1,2,3,4)</code>. Without var args
you need to construct an object array <code>log.info("This is a test {} , {},
{}, {}",new Object[] {1,2,3,4})</code>.
@@ -582,12 +634,12 @@ of the API jar, follow the below steps.
<p>The Slf4j API bundle 1.7.x is binary compatible with 1.6.x.</p>
<p>This setup allows your bundles to make use of the var args feature while
making logging calls, but the bundles
can still be deployed on older systems which provide only the 1.6.4 version of
the slf4j api.</p>
-<h2 id="log-tracer">Log Tracer</h2>
+<h2 id="log-tracer">Log Tracer<a class="headerlink" href="#log-tracer"
title="Permanent link">¶</a></h2>
<p>Log Tracer provides support for enabling the logs for specific category at
specific
level and only for specific request. It provides a very fine level of control
via config provided
as part of HTTP request around how the logging should be performed for given
category.</p>
<p>Refer to <a href="/documentation/bundles/log-tracers.html">Log Tracer
Doc</a> for more details</p>
-<h2 id="slf4j-mdc">Slf4j MDC</h2>
+<h2 id="slf4j-mdc">Slf4j MDC<a class="headerlink" href="#slf4j-mdc"
title="Permanent link">¶</a></h2>
<p>Sling MDC Inserting Filter exposes various request details as part of <a
href="http://www.slf4j.org/manual.html#mdc";>MDC</a>.</p>
<p>Currently it exposes following variables:</p>
<ol>
@@ -604,7 +656,7 @@ as part of HTTP request around how the l
Look for configuration with name 'Apache Sling Logging MDC Inserting Filter'
for details on
specifying header, cookie, param names.</p>
<p><img alt="MDC Filter Config"
src="/documentation/bundles/mdc-filter-config.png" /></p>
-<h3 id="installation">Installation</h3>
+<h3 id="installation">Installation<a class="headerlink" href="#installation"
title="Permanent link">¶</a></h3>
<p>Download the bundle from <a
href="http://sling.apache.org/downloads.cgi";>here</a> or use following Maven
dependency</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.sling<span
class="nt"></groupId></span>
@@ -614,7 +666,7 @@ specifying header, cookie, param names.<
</pre></div>
-<h2 id="logback-groovy-fragment">Logback Groovy Fragment</h2>
+<h2 id="logback-groovy-fragment">Logback Groovy Fragment<a class="headerlink"
href="#logback-groovy-fragment" title="Permanent link">¶</a></h2>
<p>This fragment is required to make use of Groovy based event evaluation
support
provided by Logback. This enables programatic filtering of the log messages and
is useful to get desired logs without flooding the system. For example Oak
@@ -658,7 +710,7 @@ event. Above logback config would route
category to <code>${sling.home}/logs/oak.log</code>. Further only those log
messages would be logged
where the <code>threadName</code> contains <code>JobHandler</code>. Depending
on the requirement the expression can
be customised.</p>
-<h3 id="installation_1">Installation</h3>
+<h3 id="installation_1">Installation<a class="headerlink"
href="#installation_1" title="Permanent link">¶</a></h3>
<p>Currently the bundle is not released and has to be build from <a
href="http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/logback-groovy-fragment/";>here</a></p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.sling<span
class="nt"></groupId></span>
@@ -668,8 +720,8 @@ be customised.</p>
</pre></div>
-<h2 id="faq">FAQ</h2>
-<h5 id="q-can-sling-commons-log-bundle-be-used-in-non-sling-environments">Q.
Can Sling Commons Log bundle be used in non Sling environments</h5>
+<h2 id="faq">FAQ<a class="headerlink" href="#faq" title="Permanent
link">¶</a></h2>
+<h5 id="q-can-sling-commons-log-bundle-be-used-in-non-sling-environments">Q.
Can Sling Commons Log bundle be used in non Sling environments<a
class="headerlink"
href="#q-can-sling-commons-log-bundle-be-used-in-non-sling-environments"
title="Permanent link">¶</a></h5>
<p>This bundle does not depend on any other Sling bundle and can be easily
used in any OSGi framework.
To get complete log support working you need to deploy following bundles</p>
<ul>
@@ -679,26 +731,12 @@ To get complete log support working you
<li>Sling Log Service -
org.apache.sling:org.apache.sling.commons.logservice:1.0.2</li>
<li>Sling Commons Log - org.apache.sling:org.apache.sling.commons.log:4.0.0 or
above</li>
</ul>
-<h5 id="q-how-to-start-sling-with-an-external-logbackxml-file">Q. How to start
Sling with an external logback.xml file</h5>
+<h5 id="q-how-to-start-sling-with-an-external-logbackxml-file">Q. How to start
Sling with an external logback.xml file<a class="headerlink"
href="#q-how-to-start-sling-with-an-external-logbackxml-file" title="Permanent
link">¶</a></h5>
<p>You need to specify the location of logback.xml via
<code>org.apache.sling.commons.log.configurationFile</code></p>
<div class="codehilite"><pre> <span class="n">java</span> <span
class="o">-</span><span class="n">jar</span> <span class="n">org</span><span
class="p">.</span><span class="n">apache</span><span class="p">.</span><span
class="n">sling</span><span class="p">.</span><span
class="n">launchpad</span><span class="o">-</span><span
class="n">XXX</span><span class="o">-</span><span
class="n">standalone</span><span class="p">.</span><span class="n">jar</span>
<span class="o">-</span><span class="n">Dorg</span><span
class="p">.</span><span class="n">apache</span><span class="p">.</span><span
class="n">sling</span><span class="p">.</span><span
class="n">commons</span><span class="p">.</span><span
class="nb">log</span><span class="p">.</span><span
class="n">configurationFile</span><span class="p">=</span><span
class="o">/</span><span class="n">path</span><span class="o">/</span><span
class="n">to</span><span class="o">/</span><span class="n">logback</span>
</pre></div>
-
-
-<h2 id="webconsole-plugin">WebConsole Plugin</h2>
-<p>The Web Console Plugin supports the following features:</p>
-<ul>
-<li>Display the list of loggers which have levels or appenders configured.</li>
-<li>List the file appenders with the location of current active log files.</li>
-<li>Show the contents of LogBack config files.</li>
-<li>Show the contents of various Logback config fragments.</li>
-<li>Show Logback Status logs.</li>
-<li>Inline edit the Logger setting</li>
-<li>Configure Logger with content assist for logger names</li>
-</ul>
-<p><img src="sling-log-support.png" /></p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1681061 by chetanm on Fri, 22 May 2015 09:54:08 +0000
+ Rev. 1692853 by chetanm on Mon, 27 Jul 2015 10:08:25 +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/sling-log-support.png
==============================================================================
Binary files - no diff available.
