πŸ“„2. Guardpot Platform Administration

2.8 Load Tester Module

3 min read67 viewsUpdated May 20, 2026

The Load Tester module performs bandwidth and stress tests against specified targets to evaluate infrastructure resilience, as shown in Figure 2.8-1.

Figure 2.8-1 – Load Tester Interface


2.8.1 Latest Load Test Card

Upon entering the Load Tester module, the most recently executed test is displayed prominently in the Latest Load Test card at the top-left of the interface, as shown in Figure 2.8.1-1.

Figure 2.8.1-1 – Latest Load Test Card

The card displays a summary of the most recent test with the following information:

Field

Description

Test Name

Identifier for the test (e.g., "pop")

Type

Test category (e.g., Bandwidth)

Date

Execution date (e.g., 3/16/2026)

URL

Target destination (e.g., 194.xxx.xxx.xxx)

Port

Target service port (e.g., 443)


2.8.2 Load Tests Table

Below the Latest Load Test card, the Load Tests section displays all executed tests in a table with grouping capabilities, as shown in Figure 2.8.2-1.

Figure 2.8.2-1 – Load Tests Table

Figure 2.8.2-1 – Load Tests Table

2.8.2.1 Search and Grouping

A Search text bar at the top of the table allows you to filter tests by name or other criteria. Tests can be organized into grouped views. The group header displays:

Grouped Test (2 Total Results)

Each group can be expanded or collapsed using the circle indicator to show or hide its contained tests.

2.8.2.2 Table Columns

Column

Description

Name

Test identifier (e.g., "pop2 Guardpots")

Type

Bandwidth or DDoS

Date

When the test was executed (e.g., 3/16/2026)

Actions

Edit and Delete buttons


2.8.3 Creating a New Load Test

To create a new load test, click the New Load Test button located at the top of the module. The test creation wizard opens with a two-step process, as shown in Figure 2.8.3-1.

Figure 2.8.3-1 – New Load Test Wizard - Step 1

Figure 2.8.3-1 – New Load Test Wizard - Step 1

The wizard is titled "Create Attack" with the subtitle "Fill required details below to continue."

2.8.3.1 Step 1: Target Selection

The first step displays available Guardpot agents that will execute the test. Each agent card shows:

Field

Description

Agent Name

The honeypot agent available for testing (e.g., "Auto Detected", "onur2", "Test")

Continent

Geographic continent (displays "Unknown" if not set)

Country

Geographic country (displays "Unknown" if not set)

City

Geographic city (displays "Unknown" if not set)

Select the desired source agent and click Next to proceed to Step 2.

2.8.3.2 Step 2: Test Configuration

The second step configures the test parameters. The available fields vary depending on the selected Attack Type, as shown in Figure 2.8.3.2-1.

Figure 2.8.3.2-1 – New Load Test Wizard - Step 2

Figure 2.8.3.2-1 – New Load Test Wizard - Step 2

The following parameters are common to both attack types:

Parameter

Description

Name

A descriptive identifier for the test

Attack Type

Select Bandwidth or DDoS

Data Type

Protocol selection (HTTP, HTTPS, TCP, or UDP)

Address

Target URL or IP address for the test

Port

Target service port number


2.8.3.2.1 Bandwidth Attack Configuration

When Bandwidth is selected as the Attack Type, the following additional parameters appear, as shown in Figure 2.8.3.2.1-1.

Figure 2.8.3.2.1-1 – Bandwidth Attack Configuration

Parameter

Description

Bandwidth (per honeypot throughput)

The amount of data each honeypot sends per second to the target

Duration (seconds)

Total runtime for the bandwidth test


2.8.3.2.2 DDoS Attack Configuration

When DDoS is selected as the Attack Type, the following additional parameters appear, as shown in Figure 2.8.3.2.2-1.

Figure 2.8.3.2.2-1 – DDoS Attack Configuration

Parameter

Description

Request Schema

HTTP request schema to use for the attack

Count (total requests per Guardpot)

Total number of requests each honeypot sends to the target


Click Save to start the test immediately. The test will appear in the Load Tests table once execution begins.

Was this article helpful?

Your feedback helps us improve our documentation.

Send feedback