You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by se...@apache.org on 2016/05/06 16:17:49 UTC
svn commit: r1742560 - /jmeter/trunk/xdocs/usermanual/realtime-results.xml
Author: sebb
Date: Fri May 6 16:17:49 2016
New Revision: 1742560
URL: http://svn.apache.org/viewvc?rev=1742560&view=rev
Log:
Fix up metric names - JMeter does not automatically add "." after the root name prefix
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=1742560&r1=1742559&r2=1742560&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/realtime-results.xml (original)
+++ jmeter/trunk/xdocs/usermanual/realtime-results.xml Fri May 6 16:17:49 2016
@@ -55,46 +55,46 @@ In this document we will present the con
Threads metrics are the following:
</p>
<dl>
- <dt><code><rootMetricsPrefix>.test.minAT</code></dt><dd>Min active threads</dd>
- <dt><code><rootMetricsPrefix>.test.maxAT</code></dt><dd>Max active threads</dd>
- <dt><code><rootMetricsPrefix>.test.meanAT</code></dt><dd>Mean active threads</dd>
- <dt><code><rootMetricsPrefix>.test.startedT</code></dt><dd>Started threads</dd>
- <dt><code><rootMetricsPrefix>.test.endedT</code></dt><dd>Finished threads</dd>
+ <dt><code><rootMetricsPrefix>test.minAT</code></dt><dd>Min active threads</dd>
+ <dt><code><rootMetricsPrefix>test.maxAT</code></dt><dd>Max active threads</dd>
+ <dt><code><rootMetricsPrefix>test.meanAT</code></dt><dd>Mean active threads</dd>
+ <dt><code><rootMetricsPrefix>test.startedT</code></dt><dd>Started threads</dd>
+ <dt><code><rootMetricsPrefix>test.endedT</code></dt><dd>Finished threads</dd>
</dl>
</subsection>
<subsection name="§-num;.1.2 Response times metrics" anchor="metrics-response-times">
<p>Response related metrics are the following:</p>
<dl>
- <dt><code><rootMetricsPrefix>.<samplerName>.ok.count</code></dt>
+ <dt><code><rootMetricsPrefix><samplerName>.ok.count</code></dt>
<dd>Number of successful responses for sampler name</dd>
- <dt><code><rootMetricsPrefix>.<samplerName>.h.count</code></dt>
+ <dt><code><rootMetricsPrefix><samplerName>.h.count</code></dt>
<dd>Server hits per seconds, this metric cumulates Sample Result and Sub results (if using Transaction Controller, "Generate parent sampler" should be unchecked)</dd>
- <dt><code><rootMetricsPrefix>.<samplerName>.ok.min</code></dt>
+ <dt><code><rootMetricsPrefix><samplerName>.ok.min</code></dt>
<dd>Min response time for successful responses of sampler name</dd>
- <dt><code><rootMetricsPrefix>.<samplerName>.ok.max</code></dt>
+ <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>
+ <dt><code><rootMetricsPrefix><samplerName>.ok.pct<percentileValue></code></dt>
<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>
+ <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>
+ <dt><code><rootMetricsPrefix><samplerName>.ko.min</code></dt>
<dd>Min response time for failed responses of sampler name</dd>
- <dt><code><rootMetricsPrefix>.<samplerName>.ko.max</code></dt>
+ <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>
+ <dt><code><rootMetricsPrefix><samplerName>.ko.pct<percentileValue></code></dt>
<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>
+ <dt><code><rootMetricsPrefix><samplerName>.a.count</code></dt>
<dd>Number of responses for sampler name</dd>
- <dt><code><rootMetricsPrefix>.<samplerName>.a.min</code></dt>
+ <dt><code><rootMetricsPrefix><samplerName>.a.min</code></dt>
<dd>Min response time for responses of sampler name</dd>
- <dt><code><rootMetricsPrefix>.<samplerName>.a.max</code></dt>
+ <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>
+ <dt><code><rootMetricsPrefix><samplerName>.a.pct<percentileValue></code></dt>
<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%.
+ i.e. the 3 percentiles 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>
@@ -103,7 +103,9 @@ In this document we will present the con
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.
+ By default JMeter sends metrics for all samplers accumulated under the samplerName "<code>all</code>".
+ If the Backend Listener <code>samplersList</code> is configured, then JMeter also sends the metrics
+ for the matching sample names unless <code>summaryOnly=true</code>
</p>
</subsection>
</subsection>
@@ -115,7 +117,7 @@ In this document we will present the con
</subsection>
<subsection name="§-num;.2 InfluxDB" anchor="influxdb">
-<p>InfluxDB is an open-source, distributed,time-series database that allows to
+<p>InfluxDB is an open-source, distributed, time-series database that allows to
easily store metrics.
Installation and configuration is very easy, read this for more details <a href="http://influxdb.com/docs/v0.8/introduction/installation.html" target="_blank" >InfluxDB documentation</a>.<br/>
InfluxDB data can be easily viewed in a browser through either <a href="https://github.com/hakobera/influga" target="_blank">Influga</a> or <a href="http://grafana.org/" target="_blank">Grafana</a>.
@@ -134,6 +136,9 @@ port = 2003
database = "jmeter" # store graphite data in this database
# udp_enabled = true # enable udp interface on the same port as the tcp interface
</source>
+ <p>
+ For later versions of InfluxDb (e.g. 0.12), replace <code>[input_plugins.graphite]</code> with <code>[[graphite]]</code>
+ </p>
</subsection>
<subsection name="§-num;.2.2 InfluxDB database configuration" anchor="influxdb_db_configuration">
<p>Connect to InfluxDB admin console and create two databases:
@@ -169,7 +174,7 @@ datasources: {
</source>
<note>
Note that grafana has "<code>grafanaDB:true</code>". Also note that here we use <code>root</code> user for simplicity
- It is better to dedicate a special user with less rights.
+ It is better to dedicate a special user with restricted rights.
</note>
Here is the kind of dashboard that you could obtain:
<figure width="1265" height="581" image="grafana_dashboard.png">Grafana dashboard</figure>