The typical output from Apache JMeter is a CSV results file, from this you can generate the default HTML report. Since the data is written to a file during test execution these are typically post test reports.

Apache JMeter does provide additional listeners which extend the reporting capabilities. One type is the backend listener where data is sent from Apache JMeter to an external repository (it’s also possible to write to CSV in parallel).

In the stock installation of Apache JMeter two backend listeners are installed for Graphite and Influxdb.

Default installed backend listeners

Graphite

Influxdb

GRAPHITE

For the graphite backend you need to supply the Graphite Host and Graphite Port. Then you can also supply the sampler list and add/amend the percentiles.

INFLUXDB

For the influxdb backend you need to supply the influxdb URL. Then you can also supply the application name and Test Title and add/remove summary and event tags.

Plugin Manager available listeners

Azure

Eleastic Search

Kafka

Jmeter Listener pack

AZURE

For the Azure backend you need to supply the test name, instrumentation key and live metrics.

ELASTIC SEARCH

For the elastic search backend you need to supply the es.host. Then you can supply a plethora of other es options which you can see on the screenshot below.

KAFKA

For the Kafka backend you need to supply the kafka.bootstrap.servers. Then you can supply a plethora of other es options which you can see on the screenshot below.

JMETER LISTENER PACK

Installs a number of backends including click house and extended elastic search and influxdb as well as providing a method of importing influxdb data.

Click House

Elastic Search

Influxdb

Influxdb Import File Client

FURTHER READING

JMeter Backend Listener Documentation