Test Run Details

For each test run, we provide a detailed report page with visualizations of all the collected data of the test run.

We measure with about 25 metrics per test run and process the collected data to provide a presentable information layer. The metrics include information like number of active clients, response times and request/response traffic.

Active Clients and Request Rate

The Active Clients metric displays the amount of clients that were active at a specific time (snapshot). Depending on the defined test case each client can make one or more requests. The metric Request Rate shows the total amount of requests that were made by the active clients per second.

NOTE: Very fast client sessions may start and finish before they are picked up by the snapshot and may not appear in the Active Clients metric.

Response Times (Percentile)

StormForger provides two metrics for response times. Latency Median shows the median, whereas Latency 99th Percentile displays the 99th percentile.

Traffic (Request/Response)

From the perspective of StormForger the metric Response Traffic shows the incoming traffic that is measured, whereas the metric Request Traffic shows the outgoing traffic.

Request and response traffic are always measured and displayed in transferred bytes (not bits).

Combined Graph

Displays all of the above metrics in one graph to find correlations.

HTTP Codes

Shows all HTTP Codes and their frequency of occurrence. You can filter the HTTP Codes by request tag.

Other Errors and Events

There are a couple of events and errors that are not related to HTTP errors. In this chart we present those events over time.

  • connect: retry limit reached: The retry limited was reached and no TCP connection could be established
  • connect: ECONNREFUSED: The connection was refused
  • connect: ETIMEOUT: A timeout occurred before the connection could be established
  • connect: ENXDOMAIN: The target (host) could not be resolved.
  • request: connection closed while sending
  • request: send retry limit reached: The agent gave up sending the request
  • response: body size, Content-Length mismatch: The size of the received content body from your endpoint did not match the Content-Length response HTTP header
  • response: JSON expected: The response could not be parsed as JSON although JSONPath content extraction was requested


  • connect: EMFILE and connect: EADDRINUSE: These errors occur mostly due to overloading the load generating cluster; try to increase the cluster size and try again

Statistics by Arrival Phase

If you've defined more than one arrival phase you get a statistics summary for each arrival phase with information about requests count, apdex, mean & stddev, median, percentiles (95th, 99th) and errors.

Statistics by Request Tag

If you've defined tags on your requests you get a statistics summary for each tag with information about requests count, apdex, mean & stddev, median, percentiles (95th, 99th) and errors. Requests that are not tagged will appear as -default-.


The last table in the report shows a list of all performed checks and assertions. It presents the name, the total number of performed checks (across all phases) and their success/failures counters and rate.

Icon Support Are you stuck? Or do you have any feedback? Get in touch with us – we are happy to help you.
Icon Schedule a demo Schedule a personal, customized demo. We'll show you around and introduce you to StormForger.
Icon Talk to a human To build and run reliable applications is complex – we know. Schedule a call and we’ll figure things out.

We are using cookies to give you the best online experience. If you continue to use this site, you agree to our use of cookies. By declining we will disable all but strictly required cookies. Please see our privacy policy for more details.

Accept Decline