svn commit: r871712 - in /websites/staging/sling/trunk/content: ./ documentation/bundles/sling-health-check-tool.html

[bu...@apache.org]

Author: buildbot
Date: Mon Jul 29 13:59:36 2013
New Revision: 871712

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/documentation/bundles/sling-health-check-tool.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 29 13:59:36 2013
@@ -1 +1 @@
-1508044
+1508072

Modified: websites/staging/sling/trunk/content/documentation/bundles/sling-health-check-tool.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/bundles/sling-health-check-tool.html (original)
+++ websites/staging/sling/trunk/content/documentation/bundles/sling-health-check-tool.html Mon Jul 29 13:59:36 2013
@@ -113,7 +113,27 @@ plugin form, or using them as selectors 
 tags and optionally showing only results from rules that have something to report (as in "no news is good news").</p>
 <p>The screenshot below shows an example, as of svn revision 1490286.</p>
 <p><img alt="" src="sling-hc-plugin.jpg" /></p>
-<h2 id="jmx-access-to-health-check-rules-results">JMX access to Health Check Rules results</h2>
+<h2 id="jmx-interfaces">JMX interfaces</h2>
+<h3 id="accessing-and-combining-jmx-attributes-in-scripted-rules">Accessing and combining JMX attributes in scripted rules</h3>
+<p>Although the basic <em>jmxbeans</em> rules give access to single JMX attribute values in rules, a more powerful way to access
+JMX attributes is to use scripted rules, where mini-scripts can be written to combine and check multiple values.</p>
+<p>The rule definition shown below, for example, checks two JMX attributes. Such scripted rules can be written in any scripting language
+that Sling supports, which allows for creating rules that check JMX attributes against other values.</p>
+<div class="codehilite"><pre><span class="p">{</span>
+    &quot;<span class="n">sling</span><span class="p">:</span><span class="n">resourceType</span>&quot; <span class="p">:</span> &quot;<span class="n">sling</span><span class="o">/</span><span class="n">healthcheck</span><span class="o">/</span><span class="n">rules</span>&quot;<span class="p">,</span>
+    &quot;<span class="n">namespace</span>&quot;<span class="p">:</span> &quot;<span class="n">script</span>&quot;<span class="p">,</span>
+    &quot;<span class="n">ruleName</span>&quot;<span class="p">:</span> &quot;<span class="n">Example</span> <span class="n">javascript</span> <span class="n">expression</span> <span class="n">that</span> <span class="n">combines</span> <span class="n">two</span> <span class="n">JMX</span> <span class="n">attributes</span>&quot;<span class="p">,</span>
+    &quot;<span class="n">qualifier</span>&quot;<span class="p">:</span> &quot;<span class="n">ecma</span>&quot;<span class="p">,</span>
+    &quot;<span class="n">expression</span>&quot;<span class="p">:</span> 
+        <span class="s">&#39;jmx.attribute(&quot;java.lang:type=ClassLoading&quot;, &quot;LoadedClassCount&quot;) &gt; 100 </span>
+<span class="s">        &amp;&amp; jmx.attribute(&quot;osgi.core:type=framework,version=1.5&quot;,&quot;FrameworkStartLevel&quot;) &gt; 1&#39;</span><span class="p">,</span>
+    &quot;<span class="n">tags</span>&quot; <span class="p">:</span> <span class="p">[</span>&quot;<span class="n">script</span>&quot;<span class="p">,</span>&quot;<span class="n">javascript</span>&quot;<span class="p">,</span> &quot;<span class="n">jmx</span>&quot; <span class="p">],</span>
+    &quot;<span class="n">jcr</span><span class="p">:</span><span class="n">primaryType</span>&quot;<span class="p">:</span> &quot;<span class="n">nt</span><span class="p">:</span><span class="n">unstructured</span>&quot;
+<span class="p">}</span>
+</pre></div>
+
+
+<h3 id="jmx-access-to-health-check-rules-results">JMX access to Health Check Rules results</h3>
 <p>Creating  <em>org.apache.sling.hc.sling.impl.RulesMBeans</em> OSGi configurations causes the results of health 
 check rules to be made available via JMX MBeans in the <em>org.apache.sling.healthcheck</em> JMX tree.</p>
 <p>The slingdemo module provides an example configuration, which is used in the screenshot below.</p>
@@ -128,7 +148,7 @@ data is read-only.</p>
 <h2 id="known-issues">Known issues</h2>
 <p>See <a href="https://issues.apache.org/jira/browse/SLING-2822">SLING-2822</a> for details.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1508044 by bdelacretaz on Mon, 29 Jul 2013 13:08:49 +0000
+        Rev. 1508072 by bdelacretaz on Mon, 29 Jul 2013 13:59:28 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project