G
G
Guides
Go to Dashboard
Search…
G
G
Guides
Getting started with Flood
Overview of Flood
Scripting and Tools
Choosing a tool
Test Builder
JMeter
Gatling
Flood Element
Selenium
Default tool versions
Test data
Accessing the file system
Saving custom results
Custom libraries
Supported SSL ciphers
Infrastructure
Infrastructure overview
Demand infrastructure
Host Your Own infrastructure
Standalone Infrastructure: Flood Agent
Flood's network topology
Grid management
How to get the IP address of your grid node
Static IP addresses
Test Execution
Infrastructure
Test parameters
Advanced parameters
Environment variables
Baselining
Using the Flood API
Overriding DNS
Planning for a large-scale test
Troubleshooting: Test Execution
Results Analysis
Metrics during test
Project view
Flood view
Transaction detail view
Grid resource utilization
Flood options
Service Level Objectives
Archived Results
Sharing results
CSV Results
Troubleshooting: Results Analysis
Continuous Integration
Continuous Integration with Flood
Travis CI
Circle CI
Jenkins
APM Tools
Account Management
Managing account members
Managing account resources
Single Sign On (SSO)
Reset your password
Troubleshooting: Account Management
Pricing
How much does it cost?
What is a VUH?
Billing page
Usage page
Pricing FAQ
Why don't I see a VUH estimate?
Minimizing costs on Flood
Tosca
Using Tosca with Flood
Ebooks
API Load Testing: A Beginner's Guide
Powered By GitBook
Flood view
Seeing the overall metrics for one flood
The Flood view is very similar to the project view, but it only shows details about the flood that is selected.​​
A. The status of the flood is displayed in icon form. You can hover over the icon to see what it means. A flood can have the follow statuses:
  • Stopping (square) - The flood is in the process of stopping, and is waiting for the last responses or copying results to Flood.
  • Completed (check icon) - The flood has stopped.
  • Problem (triangle with an exclamation point) - An error was encountered during the flood.
B. The project name, flood name and flood number are now shown in the upper left.
C. Timeline is shown by default, and contains the graph as pictured in the screenshot above.
D. Logs shows the data written to files on the nodes and may contain important information used to debug errors.
Could not load image
The Logs tab is populated in real-time while a test is running, but you can also download the full logs.
E. The grids used in a flood are shown in a dropdown menu.​
Could not load image
All grids will be shown in this menu along with their identifying name ("hydrodynamic-blackburn" in this example) and the number of nodes in each grid. Clicking on the grid in this menu will show only information from that grid. This can be useful when wanting to compare, for example, the effect of geographic location of the grids on response time.
When more grids are used, an option to select "All Grids" will be displayed. You can select this option to see the test as a whole.
F. The flood options menu is to the right of the Grids dropdown menu.​
​
​
G. The list of transactions sits below the graph and shows all the transactions executed in that flood, along with each one's response time, throughput, and error rate. The transactions are sorted from highest response time to the lowest by default to highlight potential problem transactions.
Clicking on the > arrow to the right of each transaction will take you to the transaction detail view.​​
Previous
Project view
Next
Transaction detail view
Last modified 2yr ago
Copy link