You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* New feature: added the possibility to manage response body length. Improved the results saving
1. Removed nulls - now the string "noData" instead of null to simplify the results sorting; null is not supported in the query - it seems :).
2. Added the "result" tag to filter the results quickly, can be "pass" or "fail".
* Fixes after dev testing, updated the README.md, the dashboard.
* Fixes after dev testing, updated the README.md, the dashboard.
Co-authored-by: Mikhail.Derevyanko <[email protected]>
* Java 11 - make sure that you have it (its minimum version).
56
58
* InfluxDB v2.0, see release notes: https://docs.influxdata.com/influxdb/v2.0/reference/release-notes/influxdb/ (1.8 is not supported)
57
59
* JMeter 5.4.3 only.
58
-
* The current board and plugin were tested on Grafana 8.2.3 and InfluxDB 2.0.9, JAVA 15.
60
+
* The current board and plugin were tested on Grafana 8.5.4 and InfluxDB 2.2.0, JAVA 15.
59
61
60
62
## Maven Support
61
63
Please see the latest release here https://search.maven.org/artifact/io.github.mderevyankoaqa/jmeter-plugins-influxdb2-listener.
@@ -94,36 +96,41 @@ While the first pull request please add your self to the [build.gradle](https://
94
96
95
97
Note: "fatJar" gradle task should be used to create the package for the JMeter.
96
98
97
-
99
+
98
100
99
101
* Run JMeter and select the test plan, Add-> Listener -> Backend Listener.
100
102
101
-
103
+
102
104
105
+
* Go to Backend Listener
106
+
107
+
108
+
103
109
* Select from the dropdown item with the name '`io.github.mderevyankoaqa.influxdb2.visualizer.JMeterInfluxDBBackendListenerClient`'.
104
-
105
-
110
+
111
+
106
112
107
113
## Upgrade
108
114
* Close JMeter if its started.
109
115
* Remove old jar.
110
116
* Put '`jmeter-plugin-influxdb2-listener-<version>.jar`' file from [Releases](https://github.com/mderevyankoaqa/jmeter-influxdb2-listener-plugin/releases) to `~<JmeterPath<\lib\ext`;
111
117
* Run JMeter again and got Listener.
112
118
* Select from the dropdown item with the name '`io.github.mderevyankoaqa.influxdb2.visualizer.JMeterInfluxDBBackendListenerClient`'.
113
-
119
+
120
+
121
+
114
122
* Click 'Clear all' button
115
123
116
-
124
+
117
125
* Set right settings (update all properties).
118
126
119
127
## InfluxDB configuration
120
128
* Create Bucket to store the further testing results.
121
129
122
-
130
+
123
131
124
132
* Create the token with read and write rights.
125
-
126
-
133
+
127
134
128
135
## Plugin configuration
129
136
Let’s explain the plugin fields:
@@ -134,32 +141,30 @@ Let’s explain the plugin fields:
134
141
*`influxDBHost` - the host name or ip of the InfluxDB server.
135
142
*`influxDBPort` - the port of the InfluxDB server, the default is 8086.
136
143
*`influxDBToken` - the influxdb bucket token, the default value should be updated, copy it from InfluxDB site.
137
-
*`influxDBFlushInterval` - its interval to send data to InfluxDB, the default value is 4000 (4 seconds).
138
-
*`influxDBMaxBatchSize` - the max size of the batch with metrics, the default 2000 (2000 items of JMeter results).
139
-
*`influxDBThresholdError` - the error threshold before stopping the import, the default value is 5. (see [Important notes](https://github.com/mderevyankoaqa/jmeter-influxdb2-listener-plugin/tree/main#important-notes) for more detail.)
140
144
141
-
145
+
142
146
143
147
*`influxDBOrganization` - the influxdb bucket organization, the default value should be updated, copy it from InfluxDB site.
144
148
145
-
146
-
149
+
150
+
151
+
*`influxDBFlushInterval` - its interval to send data to InfluxDB, the default value is 4000 (4 seconds).
152
+
*`influxDBMaxBatchSize` - the max size of the batch with metrics, the default 2000 (2000 items of JMeter results).
153
+
*`influxDBThresholdError` - the error threshold before stopping the import, the default value is 5. (see [Important notes](https://github.com/mderevyankoaqa/jmeter-influxdb2-listener-plugin/tree/main#important-notes) for more detail.)
147
154
*`influxDBBucket` - the InfluxDB bucket name to store the test results.
148
155
*`samplersList` - the regex value to sort out the JMeter samplers results; the default is _`.*`_. For example if you have the pattern of JMeter test plan development like this - create the 'Transaction controller', add inside of the 'Transaction controller' the Sampler with request, and the name pattern '`GET->Something`', like on the see screen below.
149
-
150
-
151
-
152
156
The regex `^(Home Page|Login|Search)(-success|-failure)?$` can be used to save only samplers names. The regex can be generated from JMeter menu.
153
157
154
-
158
+
155
159
156
160
You can modify the generated string in terms of your purposes.
157
161
158
-
162
+
159
163
160
164
*`useRegexForSamplerList` - allows to use the regexps if set to 'true'.
161
165
*`recordSubSamples` - allows to save the JMeter sub samples if set to 'true'.
162
166
*`saveResponseBodyOfFailures` - allows to save the response body of the failures.
167
+
*`responseBodyLength` - allows saving the response body, not more than the set specified length.
163
168
164
169
## Sending metrics performance tuning
165
170
The plugin imports batch with JMeter results each 4 seconds (by default settings). In the logs you will see records like this:
@@ -178,32 +183,32 @@ See deployment instructions here https://grafana.com/grafana/dashboards/13644
178
183
179
184
Dashboard helps:
180
185
* Monitor throughput with active users.
181
-
182
-
186
+
183
187
184
-
* Overview and analise the response time, distribution as well.
185
-
186
-
187
188
188
-
189
+
* Overview and analise the response time, distribution as well. Added the filters to see requests with status "pass", "fail".
190
+
191
+
189
192
193
+
190
194
* See aggregate report.
191
195
The table rendering may take an extra time. The table has hardware resources consuming queries from Influxdb side. If you have low hardware on the Influxdb server - recommended make the clone of the original dashboard and remove aggregate report.
192
196
So the idea - it's to have one 'fast' dashboard for the online monitoring (has no aggregate report) to see the results while the test, the second (original with aggregate report) to see the final results.
197
+
193
198
194
-
199
+
Now added the possibility to see the aggregate report for requests with status "pass" only.
200
+
195
201
196
-
* Investigate errors. The table is interactive, it's possible to filter data in the columns and see details for the specific error.
197
202
198
-
203
+
* Investigate errors. The table is interactive, it's possible to filter data in the columns and see details for the specific error. Added the paging.
204
+
199
205
200
-
* See network statistics, latency, processing time.
201
-
202
-
203
-
204
-
* Check individual request details.
205
-
206
-
207
206
207
+
* See network statistics, latency, processing time.
0 commit comments