-
-
Notifications
You must be signed in to change notification settings - Fork 76
Home
Anthony Gauthier edited this page Jul 16, 2018
·
8 revisions
JMeter ElasticSearch Backend Listener is a JMeter plugin enabling you to send test results to an ElasticSearch engine. It is meant as an alternative live-monitoring tool to the built-in "InfluxDB" backend listener of JMeter.
- ElasticSearch low-level REST client
- Using the low-level client makes the plugin compatible with any ElasticSearch version
- Bulk requests
- By making bulk requests, there are practically no impacts on the performance of the tests themselves.
- Filters
- Only send the samples you want by using Filters! Simply type them as follows in the appropriate field :
filter1;filter2;filter3
orsampleLabel_must_contain_this
.
- Only send the samples you want by using Filters! Simply type them as follows in the appropriate field :
- Verbose, semi-verbose, error only, and quiet mode
- debug : Send request/response information of all samplers (headers, body, etc.)
- info : Sends all samplers to the ElasticSearch engine, but only sends the headers, body info for the failed samplers.
- quiet : Only sends the response time, bytes, and other metrics
- error : Only sends the failing samplers to the ElasticSearch engine (Along with their headers and body information).
- Use either Kibana or Grafana to vizualize your results!
- Click here to get a sample Grafana dashboard! - All you need to do is import it into Grafana and change de data source!
- Continuous Integration support - Build comparison!
- Send custom metrics/values to your ElasticSearch! Simply add a new field in the backend listener's configuration. For example:
Name | Value |
---|---|
someKeyName | someValueToShow |
<dependency>
<groupId>io.github.delirius325</groupId>
<artifactId>jmeter.backendlistener.elasticsearch</artifactId>
<version>2.3.3</version>
</dependency>
Feel free to contribute by branching and making pull requests, or simply by suggesting ideas through the "Issues" tab.
For more information, here's a little documentation.
For any suggestions/corrections to the documentation, feel free to create an issue. Regards, delirius325.