JMeter is a popular open-source load testing tool to use when simulating a large number of users making requests to an application. This is done by software teams to help identify performance issues and bottlenecks.
Latency Lingo integrates with JMeter by reading the results log file. Once integrated, test results will be published to Latency Lingo to help you with performance test analysis and automation.
Locate your JMeter results log file. This file is a CSV generated after each test run, often with the
.jtl file extension. The file contains the following columns:
timeStamp- the time when the request was sent
elapsed- the time it took to receive the response
label- the name of the request
success- whether the request was successful or not
allThreads- the number of threads that were running at the time of the request
To generate this file in JMeter, you can either use the interface or CLI.
When using JMeter in CLI mode, you can simply provide the
-l flag with a filename.
jmeter -n -t test-plan.jmx -l 202206061137_latency_report.csv
In the interface, you can add a listener to your thread group that allows writing results to a file. I recommend the Summary Report listener.
Once added, configure that listener with your filename and the results log will be written there once the test is completed.
Run your JMeter load test as you normally would.
Once the test is completed, run the
publish command to upload the results to Latency Lingo:
latency-lingo-cli publish \
--file <jtl results file> \
--label <test name> \
--api-key <latency lingo api key> \
The test will be available in your Latency Lingo dashboard and a link is included in the CLI output:
Report can be found at https://latencylingo.com/test-runs/bdd8ce59-8c93-431f-aea9-d53d3ad03182
Now that you have integrated JMeter with Latency Lingo, you can start using the data to make informed decisions about your application performance processes. If you have any questions or need further assistance, don't hesitate to contact support.