Getting Started - Local JMeter & Gatling

Search…

Start using Flood Agent with locally installed load generators

Flood Agent can use a local installation of JMeter or Gatling to run load tests with Flood.
To use one of these local installations you need to:
create a configuration file for Flood Agent to find the location of the local installation
ensure that the local installation contains the required Flood reporting plugin.
Preparing the load generator
To allow load metrics to be collected by the Flood data ingestion pipeline, an existing load generator installation requires a Flood reporting plugin to be added.
Alternatively, we provide distributions of JMeter and Gatling, both prebundled with the plugin. 
For more information, see the specific instructions:
​JMeter​
​Gatling​
Create the configuration file
The simplest method of configuring Flood Agent is to execute the command flood-agent configure. This will start the wizard, which will ask you questions about your API token and the tools you'd like to use for this agent. At the end, it will ask you if you want it to write the config file for you. Select yes.
‌ If you prefer, you can skip the configuration wizard and create the configuration file yourself at ~/flood-agent/config.yaml . The file should have the following contents:
1
flood_api_token: flood_live_f100d1e9a8e # as grabbed above
2
tools:
3
  jmeter:
4
    jmeter_home: /path/to/jmeter_home
Copied!
Check your configuration
Next, check the configuration using the command flood-agent check . You should see something like this:
1
~# Flood Agent #~ : configuration checker
2
[>] config read from /home/user/flood-agent/config.yaml
3
​
4
==> Checking Flood API
5
[√] api token - ok
6
​
7
==> Checking tools
8
[√] jmeter - ok
9
[ ] no gatling config
10
[ ] no flood-element config
11
​
12
Next, check the configuration using the command ./flood-agent check . You should see something like this:
13
​
14
==> Checking network
15
[√] AWS S3 Archives endpoint - connectivity ok
16
[√] Flood configuration service - connectivity ok
17
[√] Flood data pipeline ingress - connectivity ok
18
[√] Flood status service - connectivity ok
19
[√] AWS sns endpoint in us-east-1 - connectivity ok
20
[√] AWS sqs endpoint in us-east-1 - connectivity ok
Copied!
If you're running flood-agent from within a corporate network, you may need to perform additional steps to get started. For more information, please see the Networking page.
Next, run a load test
To continue to launch a load test, check out Running a flood on your grid.

Getting Started - Docker

Running a Flood

Last modified 2yr ago

Copy link

Contents

Preparing the load generator

Create the configuration file

Check your configuration

Next, run a load test