JMeter - (Sampler Result | Sample | Listener (Output|Results|Data) File)

Card Puncher Data Processing


The results of a sample are showed by a listener in different ways:

  • a tree,
  • tables,
  • graphs

The sample result contains also the response data).

All listeners write the same raw data to the output file when one is specified.


In a view tree listener, a sampler result for one sample.

Jmeter Sampler Result In A View Result Tree


The same file name can be used by multiple samplers

with the same configuration


Jmeter Simple Data Writer

Result File Location

This listener can record results to a file but not to the UI. It is meant to provide an efficient means of recording data by eliminating GUI overhead.

When running in:

  • GUI mode, use the listener Simple Data Writer
  • non-GUI mode, the -l flag can be used to create a data file.

Property File / Gui


Relative Path

Relative paths can be specified to the:

  • current working directory which defaults to the bin/ directory
  • directory containing the current test plan (JMeter 2.4 and higher). The path name must begin with “~/” (or whatever specified in the JMeter property)

JMeter Properties file example:

# Prefix used to identify filenames that are relative to the current base


The “Configure” button can be used to specify:

  • whether to write it as CSV or XML.

Jmeter Log Csv Xml

  • and which fields to write to the file


The CSV log format depends on which data items are selected in the configuration. Only the specified data items are recorded in the file. The order of appearance of columns is fixed, and is as follows:

Field Description Value Example
timeStamp The end time in milliseconds since 1/1/1970. 1354223881017
elapsed in milliseconds 1858
label sampler label HTTP Request
responseCode e.g. 200, 404 200
responseMessage e.g. OK OK
threadName Thread Group 1-1
dataType e.g. text text
success true or false true
failureMessage if any
bytes number of bytes in the sample 34908
grpThreads number of active threads in this thread group 1
allThreads total number of active threads in all groups 1
Filename if a Save Response to File listener was used and is placed before any other listener
latency time to first response 132
encoding utf-8
SampleCount number of samples (1, unless multiple samples are aggregated) 1
ErrorCount number of errors (0 or 1, unless multiple samples are aggregated) 0
Hostname where the sample was generated LaptopNico
IdleTime number of milliseconds of 'Idle' time (normally 0)
Variables if specified

Default Values

The default items to be saved can be defined in the (or file.

# Results file configuration

# This section helps determine how result data will be saved.
# The commented out values are the defaults.

# legitimate values: xml, csv, db.  Only xml and csv are currently supported.

# true when field should be saved; false otherwise

# assertion_results_failure_message only affects CSV output
# response_data is not currently supported for CSV output
# Save ResponseData for failed samples

# Timestamp format
# legitimate values: none, ms, or a format suitable for SimpleDateFormat HH:mm:ss

# Put the start time stamp in logs instead of the end

# Whether to use System.nanoTime() - otherwise only use System.currentTimeMillis()

# Use a background thread to calculate the nanoTime offset
# Set this to <= 0 to disable the background thread

# legitimate values: none, first, all

# For use with Comma-separated value (CSV) files or other formats
# where the fields' values are separated by specified delimiters.
# Default:,
# For TAB, since JMeter 2.3 one can use:\t

# Optional xml processing instruction for line 2 of the file:<?xml-stylesheet type="text/xsl" href="sample.xsl"?>

# Prefix used to identify filenames that are relative to the current base

JMeter variable

JMeter variables can be saved by configuring the (or file.

The values are written to:

  • CSV files as additional columns,
  • and as additional attributes in XML files.
# Optional list of JMeter variable names whose values are to be saved in the result data files.
# Use commas to separate the names. For example:
# N.B. The current implementation saves the values in XML as attributes,
# so the names must be valid XML names.
# Versions of JMeter after 2.3.2 send the variable to all servers
# to ensure that the correct data is available at the client.

How to

read an existing results file

  • create a dummy test plan (If necessary)
  • Add the appropriate Listener (If necessary)
  • Select a file with the “Browse…” button

Documentation / Reference

Discover More
Distribution Testing Jmeter
JMeter - 2.9 - (Remote Test|Distributed testing)

In distributed testing, JMeter run in server mode on the remote node(s) that are controlled from the client. The client sends the test plan to all the servers. Then each server run it (JMeter does not...
Jmeter Classpath
JMeter - JDBC Request

Basic information on the JDBC Request. In the Test Plan Node, You can add you JDBC Driver or in the directory Jmeter_Home/lib Simple Test Plan: A Thread Group A A JmComp>#JDBC Connection...
Jmeter Listener
JMeter - Listener

A listener is a component that shows/records the results of the samples. add the Listener as a child of the sampler Or use a Simple Controller to group a set of samplers, and add a Listener. Listeners...
Card Puncher Data Processing
JMeter - Load Development LifeCycle

JMeter can download the relevant resources but it does not process the HTML and execute any Javascript functions. GUI The GUI console is for: script development and debugging only. for small...
Jmeter Response Data In A View Result Tree
JMeter - Sample Response (File|Data)

The Response file of a sampler. sampler result...
Jmeter Save Response To A File
JMeter - Save Response to File Listener

For each sample in its scope, the “Save Response to File” listener will create a file of the response Data. where: Variable Name saves the file name of the response output filelistener result...

Share this page:
Follow us:
Task Runner