Author: sebb
Date: Fri May 6 15:07:10 2016
New Revision: 1742552
URL: http://svn.apache.org/viewvc?rev=1742552&view=rev
Log:
Tweaks
Modified:
jmeter/trunk/xdocs/usermanual/realtime-results.xml
Modified: jmeter/trunk/xdocs/usermanual/realtime-results.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/realtime-results.xml?rev=1742552&r1=1742551&r2=1742552&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/realtime-results.xml (original)
+++ jmeter/trunk/xdocs/usermanual/realtime-results.xml Fri May 6 15:07:10 2016
@@ -74,9 +74,7 @@ In this document we will present the con
<dt><code><rootMetricsPrefix>.<samplerName>.ok.max</code></dt>
<dd>Max response time for successful responses of sampler name</dd>
<dt><code><rootMetricsPrefix>.<samplerName>.ok.pct<percentileValue></code></dt>
- <dd>Percentile computed for successful responses of sampler name. You can input
as many percentiles as you want (3 or 4 being a reasonable value).<br/>
- When percentile contains a comma for example "<code>99.9</code>", dot is
sanitized by "<code>_</code>" leading to <code>99_9</code>.
- By default listener computes percentiles 90%, 95% and 99%</dd>
+ <dd>Percentile computed for successful responses of sampler name. There will
be one metric for each calculated value.</dd>
<dt><code><rootMetricsPrefix>.<samplerName>.ko.count</code></dt>
<dd>Number of failed responses for sampler name</dd>
<dt><code><rootMetricsPrefix>.<samplerName>.ko.min</code></dt>
@@ -84,9 +82,7 @@ In this document we will present the con
<dt><code><rootMetricsPrefix>.<samplerName>.ko.max</code></dt>
<dd>Max response time for failed responses of sampler name</dd>
<dt><code><rootMetricsPrefix>.<samplerName>.ko.pct<percentileValue></code></dt>
- <dd>Percentile computed for failed responses of sampler name. You can input as
many percentiles as you want (3 or 4 being a reasonable value).<br/>
- When percentile contains a comma for example "<code>99.9</code>", dot is
sanitized by "<code>_</code>" leading to <code>99_9</code>.
- By default listener computes percentiles 90%, 95% and 99%</dd>
+ <dd>Percentile computed for failed responses of sampler name. There will be one
metric for each calculated value.</dd>
<dt><code><rootMetricsPrefix>.<samplerName>.a.count</code></dt>
<dd>Number of responses for sampler name</dd>
<dt><code><rootMetricsPrefix>.<samplerName>.a.min</code></dt>
@@ -94,11 +90,19 @@ In this document we will present the con
<dt><code><rootMetricsPrefix>.<samplerName>.a.max</code></dt>
<dd>Max response time for responses of sampler name</dd>
<dt><code><rootMetricsPrefix>.<samplerName>.a.pct<percentileValue></code></dt>
- <dd>Percentile computed for responses of sampler name. You can input as many
percentiles as you want (3 or 4 being a reasonable value).<br/>
- When percentile contains a comma for example "<code>99.9</code>", dot is
sanitized by "<code>_</code>" leading to <code>99_9</code>.
- By default listener computes percentiles 90%, 95% and 99%</dd>
+ <dd>Percentile computed for responses of sampler name. There will be one metric
for each calculated value.</dd>
</dl>
<p>
+ The default <code>percentiles</code> setting on the <complink name="Backend
Listener"/> is "90;95;99",
+ i.e. the 3 percentiled 90%, 95% and 99%.
+ </p>
+ <p>
+ The <a href="http://graphite.readthedocs.io/en/latest/feeding-carbon.html#step-1-plan-a-naming-hierarchy">Graphite
naming hierarchy</a>
+ uses dot (".") to separate elements. This could be confused with decimal percentile values.
+ JMeter converts any such values, replacing dot (".") with underscore ("-").
+ For example, "<code>99.9</code>" becomes "<code>99_9</code>"
+ </p>
+ <p>
By default JMeter sends only metrics for all samplers using "<code>all</code>"
as samplerName.
</p>
</subsection>
|