1. All the configuration overrides need to go to *user.properties* file
<https://jmeter.apache.org/usermanual/get-started.html#configuring_jmeter>,
this way you will protect yourself from clashes and your amendments
will survive upgrade to a newer JMeter version
2. *jmeter.save.saveservice.samplerData=true* setting will take effect
only if you switch the format of the .jtl results file
<https://cwiki.apache.org/confluence/display/JMETER/JtlFiles> to XML
so you will need to add one more line to the *user.properties* file:
*jmeter.save.saveservice.output_format=**xml*. See How to Save
Response Data in JMeter
<https://www.blazemeter.com/blog/how-to-save-response-data-in-jmeter>
article for more details.
However be aware that if you switch .jtl results file format to XML it
will lead to some consequences, for example:
* The size of file will be much larger
* JMeter will consume more resources for writing the metrics into XML
file comparing to CSV
* You won't be able to generate HTML Reporting Dashboard from the .jtl
file in XML format
So you might want to use i.e. Flexible File Writer plugin
<https://jmeter-plugins.org/wiki/FlexibleFileWriter/> instead in order
to save request data (and whatever else you wnat) into a separate file
On 9/8/2021 1:16 PM, Prateek Dua wrote:
Hi Team,
Is there any way to store payload ( POST data) of POST request in jtl / csv
file on running JMeter via command line prompt. Currently for my case, jtl
file stores only *URL* of POST request.
Though I'v enabled * jmeter.save.saveservice.samplerData=true* in both
jmeter.properties & user.properties file but POST data is not getting
stored in jtl file.
Thanks,
Prateek