We like to make it as easy as possible for you to see the results of your test, so we give you information in several places.

The Dashboard

The main thing you'll probably be interested in is the real-time dashboard of results. Here's what that dashboard looks like:

These are the metrics you can see:

Number of Concurrent Users - how many users or threads are running at a particular point in time
Response Time -
the time between sending the request and receiving the response from your application server, averaged out over all transactions by default (time to last byte)
Transaction Rate -
the number of requests executed per minute
Network Throughput
- the amount of data being successfully delivered to the grid nodes
Latency -
the amount of time it takes for a message to get from the grid nodes to your application server (time to first byte)
Passed Transactions
- the number of successful requests
Failed Transactions
- the number of requests with errors returned

If you'd like to see these metrics just for a specific instruction, simply click on the circle to the left of the transaction:

This will show you the response time and the number of passed and failed instances of this particular transaction. To switch back to seeing all transactions, simply click on the circle again to deselect it.

The Transaction Detail View

If you'd like to see more information about a particular transaction, click on the arrow at the very right of the transaction. This will take you to the Transaction Detail View, which is also populated in real time.

You can see that this gives you even more information, including response time percentiles, for the particular transaction. Scrolling down farther, you can also see the headers as well as the request and response bodies. This is a great way to see what errors you're getting and why.

Here's a more detailed explanation of the graph in this view.

The Grid Node Resource Utilization View

While a test is running, you are able to check on the resource utilization of your grid nodes. You might do this in order to determine, for example, whether you're running too many users per grid node. We recommend 1000 users per node for JMeter and Gatling and 5 users per node for Selenium, but this can depend on your application. If you attempt to put too many users through a node, it may overtax the node and cause it to behave unpredictably-- you want to be testing your application, not the grid nodes. It's good practice to also monitor your grid nodes to make sure this isn't happening so that you can trust your test results.

Simply click on the Grids button in the upper right screen in Flood.

Then click on the node you're interested in.

You will then be able to scroll down and see the CPU, Memory and I/O Utilization of that particular grid node.

Note that this view is only available while the grid node is running. If you'd like historical data, please reach out to our awesome Customer Success team and one of us will gladly help you out!

Did this answer your question?