Test Data Formats
BlazeMeter Sense supports various formats of load test log files. It is highly suggested to gzip your files before uploads. Gzipping allows larger test files to be uploaded under file size limit. Linux users should use standard gzip command, Windows users may find helpful the GNU Gzip tool.
JMeter Result Files
BlazeMeter Sense consume both XML and CSV result files from JMeter. Only 2 fields are required: timestamp and response time. Timestamp must be in Unix epoch seconds format. Additionally, if you set your JMeter to record active threads counts, you'll have corresponding rows on charts and tables. Another additional field is response code, it is used to analyze errors presence in your tests.
If you use CSV file format, make sure you have enabled field names saving in file header. It can be done by adding this line to jmeter.properties file:jmeter.save.saveservice.print_field_names=true
Figure below demonstrates recommended save setup for BlazeMeter Sense uploading:
Apache Benchmark Tool Files
Apache Benchmark tool can produce BlazeMeter Sense-compatible log format. To generate BlazeMeter Sense-compatible file please use -g command-line parameter to write a "gnuplot TSV" file. Gzip it and upload to BlazeMeter Sense.
Yandex.Tank Tool Files
BlazeMeter Sense supports Yandex.Tank performance testing tool output files. Yandex.Tank has built-in module for automatic results upload to BlazeMeter Sense
Target Resource Monitoring Data Formats
DSTAT Target Monitoring Data
For Host Monitoring Data upload you may use dstat tool CSV output. The only requirement is using --output and -T command-line switches. For example, record host resources usage with command dstat -Tcdmn --output /tmp/test.csv, then upload test.csv file as Host Monitoring Data for test.
JP@GC's PerfMon Metric Collector Data
For Host Monitoring Data upload you may use JP@GC's PerfMon data saved into CSV JTL file.
On this page: