# Introduction

PerfAgents combines distributed load test orchestration, automated UI validation under traffic, real-time performance insights, and continuous synthetic monitoring - all in one unified platform.

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FKJdj7WjFqJNJT6x5lgYW%2Fimage.png?alt=media&amp;token=bb237533-8d00-4d7e-bc8b-a54704b07322" alt=""><figcaption></figcaption></figure>

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Setup Your Account</strong></td><td><a href="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FMCIIb11nK77QWGX8YcIS%2FAccount%20Icon.png?alt=media&amp;token=75e5d29c-103f-4d1f-9dae-7c358dc64272">Account Icon.png</a></td><td><a href="/user-guide/account">Account</a></td></tr><tr><td><strong>Setup Load Test</strong></td><td><a href="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2F13aNDTm0V1VoqJ1vSbmz%2FLoad%20Orchestration%20Icon.png?alt=media&amp;token=ed76ca09-98de-4c29-bba5-91ee45441ad7">Load Orchestration Icon.png</a></td><td><a href="/user-guide/load-test-orchestration">Load Test Orchestration</a></td></tr><tr><td><strong>Setup Monitoring</strong></td><td><a href="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FOYq5KuOhUL3mxetxO11n%2FMonitoring%20Icon.png?alt=media&amp;token=fd9f0590-250a-4bd0-bae1-ef1fff2849d2">Monitoring Icon.png</a></td><td><a href="/user-guide/synthetic-monitoring">Synthetic Monitoring</a></td></tr></tbody></table>


# Explore Load Test Orchestration

PerfAgents enables teams to run scalable, distributed load tests without managing test infrastructure. It orchestrates load execution across cloud-based generator nodes to simulate real-world traffic patterns and evaluate system performance under stress.

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2Fgvgsmrqxib2cv5HbvwOw%2FLoad%20Settings%201%20(1).png?alt=media&amp;token=d0f86735-de15-4a9f-a66a-91055a599aa3" alt="Setup Load Test"><figcaption></figcaption></figure>

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2Fww4TpOaqmnkWfaxJjnlA%2FLoad%20Settings%202%201%20(1).png?alt=media&amp;token=9ce0d6b5-e6ff-4bed-8dcd-160d5803e8c5" alt=""><figcaption></figcaption></figure>

### Load Testing & Orchestration

{% stepper %}
{% step %}

#### **Distributed Stress Testing**

Evaluate performance and identify bottlenecks using scalable cloud infrastructure.
{% endstep %}

{% step %}

#### JMeter Integration

Execute standard JMeter scripts with flexible traffic modeling.
{% endstep %}

{% step %}

#### Dynamic Configuration

Adjust ramp-up, steady state, and ramp-down without script changes.
{% endstep %}

{% step %}

#### Visualized Scaling

Preview load curves and scale across multiple generator nodes and regions.
{% endstep %}

{% step %}

#### Geo-Distributed Load Testing

Generate load from multiple geographic regions to simulate distributed traffic patterns.
{% endstep %}
{% endstepper %}

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2Fj0iHJgIYleB5IvpxuvGZ%2FUI%20automation%201%20(1).png?alt=media&amp;token=2a1d52e1-7645-4f54-9368-41bd3b518eee" alt="Setup UI Execution"><figcaption></figcaption></figure>

### UI Automation within Load Tests

{% stepper %}
{% step %}

#### Hybrid Testing

Execute Playwright-based UI workflows alongside backend load tests to validate real user journeys.
{% endstep %}

{% step %}

#### Web Vitals Analysis

Measure critical metrics like LCP, FCP, TTI, and INP while systems are under stress.
{% endstep %}

{% step %}

#### Automated Triggers

Configure UI script execution based on specific time intervals or thread count thresholds.
{% endstep %}

{% step %}

#### Full Observability

Capture screenshots, videos, and traces to correlate UI performance with backend metrics.
{% endstep %}
{% endstepper %}

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2Fuw96olSdDDhNtLwUVVt3%2FAPM%20Integrations%20(1).png?alt=media&amp;token=ad16e3c8-0058-4b3b-820e-cf73b8768d60" alt=""><figcaption></figcaption></figure>

### APM Integrations

{% stepper %}
{% step %}

#### APM Monitoring

Monitor server-side metrics alongside load test execution.
{% endstep %}

{% step %}

#### Multiple APM Providers

Integrate supported APM providers for monitoring application and infrastructure performance.
{% endstep %}

{% step %}

#### Monitoring Profiles

Create and apply profiles to select the resources and metrics to be monitored during test execution.
{% endstep %}

{% step %}

#### Performance Analysis

View APM metrics alongside load test results in the Real-Time Load Test Dashboard and Timeline Report.
{% endstep %}
{% endstepper %}


# Explore Synthetic Monitoring

PerfAgents provides continuous synthetic monitoring to ensure your applications and APIs remain available, reliable, and performant at all times. It runs scheduled checks from multiple locations to detect downtime, performance degradation, and functional failures before they impact users.

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FFa3kUO4v6xeMAUHhHa65%2FCreate%20Monitoring.png?alt=media&amp;token=bbad6615-d568-4c20-8ddf-998cf5ffa638" alt="Setup Synthetic Monitoring"><figcaption></figcaption></figure>

### Website Monitoring

{% stepper %}
{% step %}

#### Availability Monitoring

Track real-time uptime and response times for critical URLs and endpoints.
{% endstep %}

{% step %}

#### SSL Management

Proactively monitor SSL certificate validity and expiration dates.
{% endstep %}

{% step %}

#### Performance Validation

Ensure continuous performance health and basic availability for key entry points.
{% endstep %}
{% endstepper %}

### REST API Monitoring

{% stepper %}
{% step %}

#### API Reliability

Monitor endpoints for availability, performance, and functional correctness.
{% endstep %}

{% step %}

#### Functional Chaining

Support multi-step requests with dynamic data passing and payload configuration.
{% endstep %}

{% step %}

#### Automated Validation

Verify responses through status code, body, and latency assertions.
{% endstep %}

{% step %}

#### Backend Health

Ensure backend service integrity with custom headers and authorization support.
{% endstep %}
{% endstepper %}

### Sequence Monitoring

{% stepper %}
{% step %}

#### Workflow Simulation

Simulate end-to-end user journeys like login, search, and checkout.
{% endstep %}

{% step %}

#### Framework Support

Execute browser-based flows using Playwright, Selenium, Puppeteer, or Cypress.
{% endstep %}

{% step %}

#### UX Validation

Continuously monitor the user experience to detect UI failures and performance regressions.
{% endstep %}
{% endstepper %}


# Account

The Account section guides you through setting up and managing your PerfAgents account. It covers everything from creating an account and setting up your organization to managing users, and user-level capabilities. This section helps you understand how access, ownership, and usage are structured across your organization.

{% stepper %}
{% step %}

### Create Account

Learn how to create your PerfAgents account and get started on the platform. This subsection explains the initial signup flow, account verification, and how your user identity is established in the system.
{% endstep %}

{% step %}

### Set Up Organization

This subsection explains how an organization is created during onboarding. It covers complete organization and user onboarding across all plans.
{% endstep %}

{% step %}

### User Roles & Access

Understand the available user roles within an organization and how access is controlled. This section explains Org Owner and Member roles, and how project-level access is assigned.
{% endstep %}

{% step %}

### PerfAgents Platform

This section provides the PerfAgents platform overview, highlighting its layout, navigation, and unified visibility into testing and monitoring activities.
{% endstep %}
{% endstepper %}


# Create your Account

{% embed url="<https://youtu.be/GP-9FO37z-w>" %}

#### Sign Up for PerfAgents&#x20;

To begin your journey with PerfAgents, you must first create an account:&#x20;

1. Enter your **name** in the designated field.&#x20;
2. Enter your **work email** (this will be your primary login identifier).&#x20;
3. Enter your **password** and ensure it meets the security requirements.&#x20;
4. Click the **"Sign Up"** button.&#x20;
5. A verification link will be sent to the provided work email.&#x20;
6. Confirm your account by clicking the link in the email.&#x20;
7. You will be redirected to the **“Sign In”** page. Proceed to Sign In using your **work email ID & password**.&#x20;

#### Sign In to PerfAgents&#x20;

Once your account is created and verified, you can sign in at any time:&#x20;

1. Enter your **work email** in the login field.&#x20;
2. Enter your **password**.&#x20;
3. Click the **"Sign In"** button.&#x20;
4. You will be logged into the platform and redirected to the main Dashboard.&#x20;

#### Forgot Password Flow&#x20;

If you forget your password, follow these steps to regain access to your account:&#x20;

1. Click the **"Forgot Password"** link on the sign in page.&#x20;
2. Enter your **work email** associated with your PerfAgents account.&#x20;
3. Click **"Send reset email"**. A password reset link will be sent to your email address.&#x20;
4. Confirm your reset by clicking the link in the email.&#x20;
5. You will be prompted to enter a new password:&#x20;
6. Enter the **"New Password"**&#x20;
7. Confirm the "New Password" by entering it again&#x20;
8. Confirm the password reset and proceed to Sign In using your newly created password.&#x20;


# Onboarding and Workspace Setup

After successfully signing up and verifying your email, new users are guided through a **simple 3-step onboarding process** to configure their personal profile and organization workspace. This process ensures your **free trial is activated**, and your environment is ready for performance testing. A visual progress indicator at the top of the screen helps you track your completion status.&#x20;

{% embed url="<https://youtu.be/5Uz1guJm5qY>" %}

#### Step 1: Create Your Account (Personal Information)&#x20;

The objective of this step is to capture your basic profile details.&#x20;

1. **First Name (Mandatory)**&#x20;
2. **Last Name (Mandatory)**&#x20;

**Note:** The **"Continue"** button becomes actionable only after both mandatory fields are filled. The progress indicator will show **Step 1 of 3**.&#x20;

#### Step 2: Set Up Your Workspace&#x20;

Once your personal details are complete, you will be prompted to set up your organization's workspace.&#x20;

1. You will be greeted by the name: "Welcome, \[First Name]!"
2. **Company Name (Mandatory):** This name will represent your organization and serve as the unique workspace identifier within PerfAgents.&#x20;

<table><thead><tr><th width="200.88671875">Validation Status</th><th width="312.8359375">User Experience</th><th>Actionable Item</th></tr></thead><tbody><tr><td>Name is Already Taken </td><td>The input field is highlighted in red with the error message: "[Company Name] is already taken by someone else in your company. Please try a different name. A suggested alternative name is automatically generated. </td><td>Users can accept the suggestion or enter a different custom name. </td></tr><tr><td>Name is Available </td><td>A green validation checkmark appears next to the field. | User can proceed by clicking. </td><td>Continue </td></tr></tbody></table>

#### Step 3: Final Confirmation & Trial Activation&#x20;

This final step confirms your setup and activates your free trial.&#x20;

1. You will see a completion screen: "You’re all set! Ready to start your free trial?"&#x20;
2. A confirmation message reinforces the successful setup: "Welcome to PerfAgents, \[First Name]! We're excited to help you optimize your performance."&#x20;

Clicking **“Start Free Trial”** finalizes the process:&#x20;

1. The organization's workspace is created.&#x20;
2. You are assigned as the Organization Owner.&#x20;
3. The free trial period begins.&#x20;
4. You are immediately redirected to the PerfAgents dashboard.&#x20;


# User Roles and Permissions

PerfAgents follows a **simple, secure, single-organization access model** designed to keep ownership clear and permissions predictable.

### Organization Model

* Every PerfAgents account supports **exactly one organization**
* **One user can belong to only one organization**
* Each organization has **one mandatory Org Owner**

This model applies **uniformly across all self-served plans** (Free, Basic, or Business).

### Available Roles

PerfAgents supports **two predefined roles** within an organization:

1. Org Owner
   1. Automatically created during organization onboarding
   2. Limited to **one Org Owner per organization**
   3. Holds **full administrative control** over the organization, including users, projects, and settings
2. Member
   1. Added to the organization **only via an invite** from the Org Owner
   2. Granted access **after the invite is accepted**
   3. Does **not** have access to any projects by default and must be explicitly assigned

### Role Capabilities Overview

| Capability Area        | Org Owner                                   | Member                                                          |
| ---------------------- | ------------------------------------------- | --------------------------------------------------------------- |
| Organization settings  | Manage organization settings                | —                                                               |
| User management        | Invite and remove users                     | —                                                               |
| Project management     | Create and delete projects                  | —                                                               |
| Project access control | Assign users to projects                    | —                                                               |
| Subscription & billing | Manage plan, billing, and subscriptions     | —                                                               |
| Project access         | Access all projects within the organization | Access only explicitly assigned projects                        |
| Load testing           | Create, update, and execute load tests      | Create, update, and execute load tests (assigned projects only) |
| Monitoring             | Create, update, and execute monitoring      | Create, update, and execute monitoring (assigned projects only) |
| Results & reports      | View test results and reports               | View test results and reports (assigned projects only)          |

### Key Enforcement Rules

1. Org Owner role is **mandatory and unique**
2. Members have **no implicit project access**
3. All access is validated against:
   1. Role
   2. Project assignment
   3. Active subscription state

This ensures consistent, secure access control across all plans and subscription states

### Note

1. **Free, Basic, and Business plans** support the same role model
2. **Enterprise plans** additionally support:
   1. Advanced access controls
   2. Flexible permission management
3. Role permissions are **independent of plan limits** (projects, members, executions)


# Platform Overview

The PerfAgents Dashboard provides a high-level overview of **test executions** and **outcomes**, offering consolidated visibility into **performance testing** and **synthetic monitoring** activities. Dedicated dashboards are available for both the services, **Testing** and **Synthetic Monitoring**, each designed to present relevant metrics and execution insights. It provides visibility into **system health, active monitors, load tests, alerts,** and **usage**, all from a unified interface. &#x20;

{% embed url="<https://youtu.be/o2WLv9WdlLI>" %}

The platform is structured into two primary modules: **Load Testing** and **Monitoring**. Users can switch between these modules using the toggle in the Left Navigation Panel. \
&#x20;\
The dashboard interface consists of three primary areas:&#x20;

1. Top Header&#x20;
2. Left Navigation Panel&#x20;
3. Main Workspace Area&#x20;

#### Top Header&#x20;

The top header provides global controls and contextual information:&#x20;

1. **Organization Selector:** Displays the currently active organization and allows switching between organizations (if multi-org access is enabled).&#x20;
2. **Project Selector:** Displays the selected project within the organization. Users must select a project to view or configure data.&#x20;
3. **Trial Status Indicator:** Displays remaining trial days (e.g., “You’ve 14 days left in your trial”) and includes a visible Upgrade button.&#x20;
4. **User Profile Section:** Displays the logged-in username and role (e.g., Owner) of the user.&#x20;

#### Left Navigation Panel&#x20;

The left sidebar provides module-level navigation and feature access. At the top, users can toggle between:&#x20;

1. Testing&#x20;
2. Monitoring&#x20;

Each module displays its own contextual navigation options:&#x20;

| Module     | Navigation Options                                                                                     |
| ---------- | ------------------------------------------------------------------------------------------------------ |
| Testing    | Dashboard, Create Load Test, All Tests                                                                 |
| Monitoring | Dashboard, Create Monitoring, Alerts, Custom Variables, Whitelisted Domain, Maintenance, Holistic View |

At the bottom of the sidebar, the Plan & Usage Indicator displays the current plan (e.g., Free, Basic or Business) and shows usage limits (e.g., LG-Hours) against the subscription tier.

The main screen of the platform dynamically updates based on the selected organization, selected project, and current dashboard context.


# Audit Logs

The Audit Logs section provides a centralized record of activities performed across the PerfAgents platform. It enables organizations to track user actions, monitor system events, and maintain visibility into operational activities within the workspace.&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FU9yrd5SCbTiO5CaE0vAk%2FFrame%20243.png?alt=media&amp;token=81d5f0bb-3e14-419d-a9dd-93f4457a45b5" alt=""><figcaption></figcaption></figure>

Audit Logs help teams understand who performed an action, when the action occurred, and the associated details of the event. This improves traceability, accountability, and troubleshooting across the platform.&#x20;

### Accessing Audit Logs&#x20;

Navigate to Settings → Audit Logs to view the complete activity history for your workspace. Each audit log entry includes relevant details such as:&#x20;

* Event timestamp&#x20;
* User who performed the action&#x20;
* Activity or event type&#x20;
* Associated resource or module&#x20;
* Device or environment information (where applicable)&#x20;
* Status of the operation&#x20;


# Load Test Orchestration

The Load Test Orchestration section explains how performance tests are configured, executed, and managed in PerfAgents. It walks through creating load tests, defining execution behavior, managing test infrastructure, and analyzing results, helping you control how load is generated and evaluated across different scenarios.

{% stepper %}
{% step %}

### Create Load Test

Learn how to define user load patterns for your tests. This section explains how virtual users, ramp-up, ramp-down, peak users, and test duration are configured to simulate real-world traffic.
{% endstep %}

{% step %}

### Load Generator Configuration

This subsection explains how test execution environments are configured for distributed load testing. It covers selected regions, traffic distribution, virtual users per region, computed engine allocation, and how infrastructure scales based on test requirements.
{% endstep %}

{% step %}

### Test Execution

Understand how load tests are executed and monitored in real time. This section explains test start, stop, abort behavior, execution states, and how concurrent tests are handled.
{% endstep %}

{% step %}

### Results & Reports

This subsection focuses on analyzing test outcomes. It explains how metrics, graphs, and reports are generated and how to interpret performance results after a test completes.
{% endstep %}
{% endstepper %}


# Create Projects

{% embed url="<https://youtu.be/aWKnor4U5P4>" %}

Before creating a load test, you must either be a part of an existing project or create one of your own projects within your organization. Projects help logically group load tests.&#x20;

#### Step 1: Select or Create a Project&#x20;

From the top header:&#x20;

1. Click the **Project Selector** dropdown.&#x20;
2. You will see a **“+ Create Project”** option.&#x20;
3. Click **“+ Create Project”** to begin.&#x20;

#### Step 2: Enter Project Details&#x20;

A modal titled Create New Project will appear.&#x20;

1. **Project Name (Required):** Enter a unique name for your project (e.g., Demo Project, Production API Tests).&#x20;
2. **Description (Optional):** Provide context about the purpose of the project (e.g., “Load testing for checkout APIs.”).&#x20;

#### Step 3: Create the Project&#x20;

1. Click **Create**.&#x20;
2. The new project becomes selectable from the header.&#x20;
3. The dashboard updates to reflect the selected project.&#x20;
4. You can now create load tests within this project.&#x20;


# Setup Load Test

### What is Load Testing?&#x20;

Load testing is a critical discipline in performance engineering that involves simulating realistic user traffic and conditions to evaluate how an application behaves under stress. Its primary goal is to determine the system's capacity, identify performance bottlenecks, and ensure the application remains stable and responsive as user demand increases.

#### Significance of Load Testing:&#x20;

1. **Capacity Planning:** Determine the maximum number of users your system can handle before performance degrades.&#x20;
2. **Bottleneck Identification:** Pinpoint specific components (database queries, API endpoints, server resources) that slow down under load.&#x20;
3. **Scalability Validation:** Confirm that your infrastructure scales effectively to meet peak demand.&#x20;
4. **Risk Mitigation:** Proactively fix performance issues before they lead to production outages or poor user experience.&#x20;

PerfAgents streamlines this process by enabling you to leverage **industry-standard JMeter load tests** while seamlessly **scaling load generation** across **distributed cloud infrastructure**.&#x20;

{% embed url="<https://youtu.be/2XaLj2z3aBg>" %}

### Create Your First Load Test&#x20;

After selecting a project, you can configure and execute your first load test. Navigate to Create Load Test from the Left Navigation. The load test creation process is structured into three main configuration sections:&#x20;

### Section 1: Test Configuration&#x20;

This section defines the identity and script for your load test.

<table><thead><tr><th width="191.12890625">Field</th><th width="261.9609375">Description</th><th width="228.8671875">Example</th></tr></thead><tbody><tr><td>Test Name (Required) </td><td>A descriptive name for the test. </td><td>Homepage Load Test – Q1 </td></tr><tr><td>Description (Optional) </td><td>Explain the purpose of this test. </td><td>“Simulate 500 concurrent users during peak sale.” </td></tr><tr><td>Tags (Optional) </td><td>Add tags separated by spaces or commas for filtering. </td><td>homepage, q1, critical </td></tr></tbody></table>

#### Upload JMX File&#x20;

* PerfAgents uses JMeter (\`.jmx\`) files for load test execution.&#x20;
* Drag and drop your \`.jmx\` file or click browse.&#x20;
* Once uploaded, the file appears under “Uploaded JMX File”.&#x20;

#### Supporting Files (Optional)&#x20;

Upload any necessary files for your test, such as CSV data files, configuration files, or other resources.&#x20;

#### Test Variables&#x20;

Define key-value pairs to override variables in the JMX file, enabling execution for different configurations without modifying the script.&#x20;

| Name       | Value                         |
| ---------- | ----------------------------- |
| `base_url` | `https://staging.example.com` |

### Section 2: Load Configuration&#x20;

The Load Configuration section dynamically renders **thread group controls** based on the uploaded JMX file. Upon uploading a **JMeter script**, PerfAgents automatically **detects the thread groups** and generates customized configuration panels based on their specific types. For **multi-thread** JMeter scripts PerfAgents parses all thread groups within the file and displays dedicated configuration panels for each one. This ensures complete transparency and granular control over every execution unit within your test plan.&#x20;

#### Thread Group–Wise Configuration Rendering&#x20;

When a JMX file is uploaded:&#x20;

* PerfAgents detects all thread groups defined in the test plan.&#x20;
* Each thread group is displayed as an independent configuration block.&#x20;
* Configurations are auto-mapped based on the type of thread group.
* Users can view/modify load parameters without editing the original JMX file.

Each thread group is clearly segmented and labeled for visibility and control.&#x20;

#### Supported Thread Group Types&#x20;

PerfAgents supports multiple JMeter thread group types and renders configuration options specific to each type.&#x20;

#### Standard Test Plan Thread Group&#x20;

The Standard Test Plan Thread Group represents the traditional JMeter thread group model. It is designed for straightforward, time-based load execution where traffic follows a predictable ramp-up, steady-state duration, and optional loop behavior. This configuration is best suited for simple and controlled load testing scenarios where complex traffic staging is not required.&#x20;

#### Configurable Parameters&#x20;

1. **Virtual Users:** Defines the total number of concurrent threads (virtual users) that will execute the test plan. This represents the peak concurrency level during the test execution. Users are introduced progressively based on the ramp-up configuration.&#x20;
2. **Duration:** Specifies how long the thread group will remain active once execution begins. This allows you to define a time-bound test window (e.g., 2 minutes, 15 minutes, 30 minutes, etc.), ensuring predictable execution control.&#x20;
3. **Ramp-Up Time:** Determines how long it takes to reach the configured number of virtual users. Instead of starting all threads instantly, users are distributed evenly across the ramp-up period. For example:&#x20;

   1. 100 users with a 100-second ramp-up → 1 user starts per second.&#x20;

   This helps prevent artificial traffic spikes and simulates gradual traffic growth.&#x20;
4. **Start-Up Delay:** Defines a delay before the thread group begins execution. This is useful when:
   1. Coordinating with other thread groups&#x20;
   2. Sequencing traffic&#x20;
   3. Allowing setup tasks to complete before load injection begins&#x20;
5. **Loop Count (Including Infinite Option):** Specifies how many times each virtual user executes the test script during the active duration. Options include:&#x20;

   1. Fixed loop count (e.g., run 5 times)&#x20;
   2. Infinite loop (executes continuously until duration ends)

   The infinite option is typically used for time-based tests where sustained load is required without limiting iteration count.&#x20;

#### Visualization Support&#x20;

PerfAgents enhances the standard thread group configuration with real-time validation and visualization:&#x20;

1. **Live Thread Curve Preview:** A dynamic graph displays how virtual users will increase over time based on the configured ramp-up and duration. This allows you to:&#x20;
   1. Validate concurrency growth&#x20;
   2. Identify unintended spikes&#x20;
   3. Confirm steady-state behavior&#x20;
2. **Peak Users Display:** Automatically calculates and displays the maximum number of concurrent users defined in the configuration. This helps verify infrastructure capacity planning before execution.&#x20;
3. **Total Duration Summary:** Displays the total calculated test runtime including ramp-up and steady-state periods. This ensures clarity around actual execution time before the test is launched.&#x20;

#### Ultimate Thread Group (UTG)&#x20;

The Ultimate Thread Group (UTG) is designed for advanced traffic modeling and complex load simulation scenarios. Unlike standard thread groups that follow a simple ramp-up and duration model, UTG allows you to define multiple staged schedules within a single thread group. This makes it ideal for replicating real-world production traffic patterns where user load fluctuates over time.&#x20;

#### **Configurable Parameters**&#x20;

Each row in the UTG schedule represents a separate execution stage. You can define multiple rows to simulate phased traffic behavior.&#x20;

1. **Start Threads Count:** Defines the number of virtual users that will begin execution during that specific stage. This allows you to incrementally increase or decrease the active user count across different time windows.&#x20;
2. **Initial Delay (sec):** Specifies how long the thread group should wait before initiating that particular stage. This helps in:
   * Delaying load injection&#x20;
   * Sequencing traffic waves&#x20;
   * Staggering execution across multiple schedules&#x20;
3. **Startup Time (sec):** Determines how long it takes for the defined threads to ramp up to their full count. Instead of launching all threads instantly, they are gradually introduced over the configured duration. This prevents sudden load spikes unless intentionally configured.&#x20;
4. **Hold Load For (sec):** Defines how long the threads remain active at peak concurrency during that stage. This parameter is used to simulate steady-state traffic where user activity remains constant for a defined period.&#x20;
5. **Shutdown Time:** Controls how long it takes for the active threads to ramp down and terminate. Similar to ramp-up, threads do not stop abruptly unless configured to do so. This allows smoother load drop-offs.&#x20;

#### Visualization Support&#x20;

PerfAgents provides visual validation of your UTG configuration:&#x20;

1. **Thread Schedule Table:** Displays each configured stage with its respective timing and concurrency values.&#x20;
2. **Thread Count Over Time Graph:** Generates a real-time visualization of expected active threads based on your UTG schedule. This helps you:
   * Validate ramp patterns before execution&#x20;
   * Identify potential unintended spikes&#x20;
   * Confirm peak concurrency behavior&#x20;
3. **Peak Thread Indication:** Automatically highlights the maximum concurrent thread count derived from the defined schedules. This ensures infrastructure sizing aligns with your expected peak load.&#x20;

#### SetUp Thread Group&#x20;

The SetUp Thread Group is executed before the main load test begins. It is designed to prepare the system and environment so that the actual load phase runs under realistic and controlled conditions. Unlike the primary load thread groups, the SetUp Thread Group does not represent production traffic. Instead, it ensures that prerequisites are completed prior to load injection.&#x20;

#### Configurable Parameters&#x20;

1. **Virtual Users:** Defines how many threads will execute the setup logic. Typically, this number is smaller than the main load group unless large-scale preparation is required.&#x20;
2. **Duration:** Specifies how long the setup logic should run. This ensures the preparation phase completes within a defined time window.&#x20;
3. **Ramp-Up Time:** Controls how gradually setup threads are introduced. This can be useful when:
   1. Initializing large datasets&#x20;
   2. Avoiding sudden backend spikes during setup&#x20;
4. **Start-Up Delay:** Defines the amount of time the thread group waits before it begins execution. In simple terms, it introduces a controlled pause between the test launch and when this specific thread group starts running.&#x20;
5. **Loop Count (Including Infinite Option):** Defines how many times each setup thread executes its assigned flow. This can be:&#x20;
   1. Fixed (e.g., create 100 users)&#x20;
   2. Infinite (until duration completes)&#x20;

#### TearDown Thread Group&#x20;

The TearDown Thread Group is executed after the main load test completes. It is designed to handle post-test cleanup and environment restoration tasks. Unlike the primary thread groups that generate load, the TearDown Thread Group ensures that the system is returned to a stable and controlled state once testing finishes.&#x20;

#### Configurable Parameters&#x20;

1. **Virtual Users:** Defines how many threads will execute cleanup tasks. Typically, this is lower than the main load unless large-scale cleanup is required.&#x20;
2. **Duration:** Specifies how long the teardown logic will run. This ensures cleanup completes within a controlled time window.&#x20;
3. **Ramp-Up Time:** Determines how gradually teardown threads are introduced. Useful when cleanup actions involve backend processing and should not cause abrupt load spikes.&#x20;
4. **Start-Up Delay:** Defines how long the TearDown Thread Group waits before beginning execution after the main load test completes. This allows you to introduce a controlled pause between the end of the load phase and the start of cleanup operations.&#x20;
5. **Loop Count (Including Infinite Option):** Specifies how many times each thread executes the teardown script. Can be:&#x20;
   1. Fixed (e.g., delete 100 records)&#x20;
   2. Infinite (runs until duration ends)&#x20;

### Section 3: Load Generator Configuration&#x20;

This section allows you to select the region where the load test will be executed and define how the virtual users configured in the Load Configuration section should be distributed across those regions.&#x20;

You can distribute these users using either of the following allocation modes:&#x20;

* **Traffic %:** Distribute the total virtual users across regions based on a percentage allocation.&#x20;
* **Fixed VUs:** Assign a specific number of virtual users to each selected region.&#x20;

The system automatically calculates the Peak VUs, Total VUs, and Computed Engines based on the selected regions and configured allocation.&#x20;

#### Region Availability&#x20;

The available regions depend on the subscription plan:&#x20;

<table data-header-hidden data-search="false"><thead><tr><th>Region Name</th><th>Basic</th><th>Business</th><th>Enterprise</th></tr></thead><tbody><tr><td>US East (Ohio) </td><td>✅ </td><td>✅ </td><td>✅ </td></tr><tr><td>Canada (Central) </td><td>✅ </td><td>✅ </td><td>✅ </td></tr><tr><td>Europe (Ireland) </td><td>❌ </td><td>✅ </td><td>✅ </td></tr><tr><td>US West (Oregon) </td><td>❌ </td><td>✅ </td><td>✅ </td></tr><tr><td>US East (N. Virginia) </td><td>❌ </td><td>✅ </td><td>✅ </td></tr><tr><td>Asia Pacific (Tokyo) </td><td>❌ </td><td>✅ </td><td>✅ </td></tr><tr><td>Asia Pacific (Singapore) </td><td>❌ </td><td>✅ </td><td>✅ </td></tr><tr><td>Europe (London) </td><td>❌ </td><td>✅ </td><td>✅ </td></tr><tr><td>Europe (Frankfurt) </td><td>❌ </td><td>❌ </td><td>✅ </td></tr><tr><td>Asia Pacific (Sydney) </td><td>❌ </td><td>❌ </td><td>✅ </td></tr><tr><td>Asia Pacific (Mumbai) </td><td>❌ </td><td>❌ </td><td>✅ </td></tr></tbody></table>

**Note:** Free Plan supports single-region load testing in US East (Ohio) only.&#x20;

#### Configure Regions&#x20;

1. Select the required **regions** where the load test should be executed. &#x20;
2. Choose the allocation method from the dropdown:&#x20;
   1. **Traffic %**&#x20;
   2. **Fixed VUs**&#x20;
3. Configure the allocation for each selected region.&#x20;
4. The system automatically calculates the resulting **Peak VUs, Total VUs,** and **Computed Engines.**&#x20;
5. Use **Distribute evenly** to distribute the configured load evenly across the selected regions when required.&#x20;
6. Click **Add Region** to include additional regions.&#x20;

#### Final Step: Create Load Test &#x20;

After configuring all sections, click **Create Load Test**. The test will appear under **“All Tests”** section, ready for execution.&#x20;

### UI Automation in Load Testing

PerfAgents offers an **advanced UI Automation** feature that allows you to execute automated UI scripts alongside your load tests. This ensures that while your system is under stress, you can also validate the end-to-end user experience and UI responsiveness.&#x20;

#### UI Script Upload&#x20;

Once you have configured your basic load settings, you can navigate to the UI Automation tab to manage your automated scripts.&#x20;

1. **Upload UI Script Files:**&#x20;
   1. Drag and drop or browse your UI script files (supports .js and .ts formats).&#x20;
   2. Maximum file size: 100 MB.&#x20;
2. **UI Script Type:** Select the automation framework. Currently, PerfAgents provides robust support for Playwright.&#x20;
3. **Download Template:** A convenient option to download a sample script template to ensure your automation follows the required structure.&#x20;

#### Trigger Configuration&#x20;

The trigger configuration defines how and when your UI scripts are executed during the load test.&#x20;

<table><thead><tr><th width="178.78729248046875">Configuration</th><th>Description</th></tr></thead><tbody><tr><td>Trigger Type </td><td>Define the basis for execution (e.g., Thread Count, Time Based). </td></tr><tr><td>Peak Thread Count </td><td>It defines the peak load threshold at which the first UI script execution is initiated when Trigger Type is Thread Count. </td></tr><tr><td>Trigger After </td><td>It specifies the elapsed time after which the first UI script execution is triggered when the Trigger Type is set to Time Based. </td></tr><tr><td>Iterations </td><td>Set how many times the UI script should repeat. </td></tr><tr><td>Intervals (seconds) </td><td>Define the delay between subsequent UI script executions. </td></tr></tbody></table>

**Visual Execution Preview:** The real-time graph on the right provides a visual representation of the Virtual Users (Threads) over the Elapsed Time, helping you correlate UI automation triggers with the overall load profile.&#x20;

By integrating UI Automation, you can capture logs, and performance metrics from a real browser perspective while the backend is under heavy load.&#x20;

### APM Integrations&#x20;

PerfAgents supports integration with external Application Performance Monitoring (APM) platforms, enabling users to correlate server-side infrastructure metrics with load testing results. By combining application performance and infrastructure monitoring within a single dashboard, teams can identify bottlenecks more effectively and understand system behavior under load.&#x20;

#### Supported Integrations&#x20;

PerfAgents currently supports the following APM platforms:&#x20;

1. AWS CloudWatch &#x20;
2. Datadog &#x20;
3. Azure Monitor &#x20;
4. Dynatrace &#x20;

These integrations can be configured during load test creation and reused across multiple test executions.&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2F66m9UoyB2SjyYuIyQlLl%2F44%201.png?alt=media&amp;token=e4acbf11-f4ed-4036-aa44-1e372883a3de" alt=""><figcaption></figcaption></figure>

#### Configuring an APM Integration&#x20;

#### Step 1: Navigate to APM Integration&#x20;

While creating a load test:&#x20;

1. Upload a valid JMX file. &#x20;
2. Open the **APM Integration** section from the left panel. &#x20;

Once a JMX file is uploaded, the APM Integration module becomes available for configuration.&#x20;

#### Step 2: Select an APM Provider&#x20;

Choose the monitoring platform you want to connect. Available options include:&#x20;

1. AWS CloudWatch &#x20;
2. Datadog &#x20;
3. Azure Monitor &#x20;
4. Dynatrace &#x20;

Click “Config” on the desired integration card.&#x20;

#### Step 3: Create or Select an Existing Key&#x20;

Users can now either:&#x20;

* Create a new integration key &#x20;
* Reuse an existing configured key  &#x20;

#### Creating a new Integration Key&#x20;

<table><thead><tr><th width="206.98614501953125">APM Provider</th><th width="496.39141845703125">Required Fields</th></tr></thead><tbody><tr><td>AWS CloudWatch </td><td>Key Name, IAM Access Key ID, IAM Secret Access Key </td></tr><tr><td>Datadog </td><td>Key Name, Datadog URL, API Key, Application Key </td></tr><tr><td>Azure Monitor </td><td>Key Name, Client ID, Client Secret, Tenant ID, Subscription ID </td></tr><tr><td>Dynatrace </td><td>Key Name, Dynatrace URL, API Token </td></tr></tbody></table>

#### Step 4: Test the Connection&#x20;

After entering the required credentials:&#x20;

1. Click **Test Connection**. &#x20;
2. The Platform validates the provided credentials. &#x20;
3. Connection status is displayed immediately. &#x20;

Successful validation confirms that PerfAgents can access monitoring data from the selected platform.&#x20;

#### Step 5: Save the Integration&#x20;

Once connectivity is verified:&#x20;

1. Save the integration. &#x20;
2. The configured key becomes available for future use. &#x20;
3. Users can manage integrations from the **Settings** section. &#x20;

#### Step 6: Create an APM Profile&#x20;

After successfully configuring and validating an APM integration, create a monitoring profile that defines the infrastructure resources and server-side metrics to be tracked during load test execution. Click **Next** to navigate to the Create Profile section. The profile configuration fields vary depending on the selected APM integration:&#x20;

<table><thead><tr><th width="182.87152099609375">APM Provider</th><th width="449.09991455078125">Profile Configuration Fields</th></tr></thead><tbody><tr><td>AWS CloudWatch </td><td>Profile Name, Region, Namespace, Resources, Metrics </td></tr><tr><td>Datadog </td><td>Profile Name, Host, Entity </td></tr><tr><td>Azure Monitor </td><td>Profile Name, Region, Namespace, Resources, Metrics </td></tr><tr><td>Dynatrace </td><td>Profile Name, Entity Type, Entity, Metrics </td></tr></tbody></table>

After configuring the required fields, click **Integrate**.&#x20;

#### Step 7: Applying a Profile to a Load Test&#x20;

After a profile is created, it appears under the **Available Profiles** section for the selected APM integration. To associate a profile with the current load test:&#x20;

1. Select the desired profile using the checkbox. &#x20;
2. Click **Apply**. &#x20;
3. The selected profile is linked to the load test configuration. &#x20;

Multiple saved profiles may be available depending on the configured APM provider. &#x20;

Once applied, PerfAgents continuously collects the selected server-side metrics during test execution and displays them alongside client-side performance data within the **Real-Time Load Test Dashboard** and **Timeline Report**, enabling comprehensive infrastructure and application performance analysis.&#x20;


# Run Load Test

Once a load test is created, it is automatically added to the **All Tests** list. Newly created tests appear at the **top of the list** and are ready to be executed.

{% embed url="<https://youtu.be/N4gHurnSFd4>" %}

### Step-by-Step Execution Flow

1. **Test Creation Complete**\
   After clicking **Create Load Test**, the test is saved and you are redirected to the **All Tests** screen.
2. **Initial Test Status**\
   The newly created test appears with the status **Awaiting Execution**, indicating that the test is configured but has not yet started.
3. **Start Test Execution**\
   To begin execution, click **Run Load Test** for the selected test. Before starting a load test, users can optionally provide a **Run Name** and **Run Description** to help identify the execution.&#x20;

   Both fields are **optional** and can be updated after the test execution is completed using the **“Edit icon”**. The **Run** triggers the test execution workflow.

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FNYLyRtArqD3EhNyOMlNJ%2F46%201.png?alt=media&amp;token=7cb0592e-1583-4d5c-b33a-2f6b7ad1f1fd" alt=""><figcaption></figcaption></figure>

4. **Provisioning Progress**\
   Once the test execution is initiated, platform begins provisioning the load generators and preparing the test environment. During this process, a progress indicator is displayed which reflects the status of the provisioning and setup activities.
5. **Test Execution**\
   Once the test environment is successfully provisioned and configured, the load test execution starts automatically. The Real-Time Load Test Dashboard becomes available, enabling users to monitor execution progress and analyze performance metrics as the test runs.


# Edit Load Test

PerfAgents allows you to modify an existing load test using two editing modes: **Quick Edit** and **Detailed Edit**. This gives you flexibility to make fast configuration changes or perform deeper updates without recreating the test.

Once a load test is created, it can be edited at any time from the **All Tests** list.

### Accessing Edit Options

1. From the **All Tests** screen, locate the load test you want to modify
2. Click **Edit** icon on the selected test
3. You are presented with two editing options:
   1. Quick Edit
   2. Detailed Edit

Each option is designed for a specific level of configuration change.

### Quick Edit

Quick Edit is intended for making **fast updates to execution-related settings** without changing the core structure or definition of the test.&#x20;

{% embed url="<https://youtu.be/u7J-bsmY4pM>" %}

The following can be modified through Quick Edit:&#x20;

1. **Load Configuration:** Update load-related values such as users, duration, and ramp-up behavior.&#x20;
2. **Generator Configuration:** Update the execution-related configurations, including the region and work-load distribution settings across the regions.&#x20;
3. **UI Script Execution Trigger Configuration:** Update the trigger configuration for automated UI script execution (if configured for the test).&#x20;

Once the changes are saved, the updated test configuration is ready for execution.&#x20;

### Detailed Edit

Detailed Edit is used when you need to **modify the test definition itself** or make changes beyond the execution-related settings available in Quick Edit.

{% embed url="<https://youtu.be/Y1-iA_1bB0A>" %}

The following can be edited through Detailed Edit:&#x20;

1. **Test Setup and Structure:** Modify the overall test setup and structure.&#x20;
2. **Script or Scenario Selection:** Update the script or scenario associated with the test.&#x20;
3. **UI Automation Configuration:** Add, remove, or update UI automation configurations.&#x20;
4. **Advanced Configurations:** Modify advanced configurations defined during test creation.&#x20;
5. **APM Integrations:** Add, modify, or update the APM integrations configured for the load test.&#x20;

Selecting **Detailed Edit** redirects you to the **full test creation flow**, with the previously configured values pre-filled. After making the required changes, the test can be updated and saved.

### Updating the Load Test

1. After completing changes in either Quick Edit or Detailed Edit:
   1. Save the updated configuration
   2. The load test is updated without creating a new test entry
2. The test can again be run manually


# Live Load Test Dashboard

{% embed url="<https://youtu.be/s0E1yfbMu0A>" %}

The Live Load Test Dashboard provides a comprehensive, live view of **test execution** once a load test is initiated. It enables teams to **monitor performance** as traffic is being generated and to **analyze detailed results** immediately after completion. This dashboard serves as the central analysis workspace for understanding system behavior under load.&#x20;

All charts and graphs include interactive controls such as **Reset Zoom, Download Chart as Image,** and **Expand Chart** for deeper inspection and reporting. Additionally, tables and logs provide export options, allowing users to download execution data and log details for offline analysis and sharing.&#x20;

### 1. Test Run Overview&#x20;

The Test Run Overview provides a high-level snapshot of the executed load test, combining test configuration details with runtime execution information. It helps teams quickly understand what was executed before diving into detailed performance metrics.&#x20;

#### Test Information&#x20;

The Test Information section summarizes the core configuration of the load test:&#x20;

1. **Test Name -** The name assigned to the load test.&#x20;
2. **Total Virtual Users -** The total number of users configured to simulate concurrent traffic.&#x20;
3. **Duration -** The total configured execution time of the test.&#x20;
4. **Region -** The AWS region where the load generators were deployed.&#x20;
5. **Generators -** The number of load generator nodes used to execute the test.&#x20;

This section provides immediate context about the scale, location, and structure of the executed test.&#x20;

#### Test Run Details&#x20;

Below the Test Information section, the Test Run Details provide execution-specific metadata, including:

1. &#x20;**Run Name :** The name assigned to the specific test run.&#x20;
2. &#x20;**Start Time & End Time:** The exact execution window of the test run. &#x20;
3. &#x20;**Total Virtual Users:** The total number of virtual users applied during the test run.&#x20;
4. &#x20;**Status:** Current or final execution state (e.g., Completed, Running, Failed). &#x20;
5. &#x20;**Executed At:** Timestamp indicating when the test was triggered.&#x20;

### 2. Execution Overview&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2Fg14qlz3iUG94iqCFkdUu%2FImage%201.png?alt=media&amp;token=7b96ce4c-672b-4567-a432-4efc8cfecf85" alt=""><figcaption></figcaption></figure>

The Execution Overview provides high-level performance metrics across the entire run:&#x20;

* **Peak Virtual User's -** Number of active users during the test.&#x20;
* **Duration -** Total execution time.&#x20;
* **Sample Count -** Total number of requests processed.&#x20;
* **Avg Response Time -** Mean response time across all samples.&#x20;
* **P90 Response Time -** 90th percentile response latency.&#x20;
* **Failure Rate -** Percentage of failed requests.&#x20;
* **Throughput -** Requests processed per second.&#x20;

In addition, visual graphs display:&#x20;

* **Active Users Over Time -** Ramp-up behavior and steady-state load.&#x20;
* **Overall Samples Over Time -** Request rate trends during execution.&#x20;

These insights help quickly identify bottlenecks, spikes, and stability issues.&#x20;

### 3. Request Summary&#x20;

The Request Summary tab provides API-level performance analysis:&#x20;

**Region-Based Selection Filter** &#x20;

When multiple regions are configured for the load test, users can select the **region** for which they want to view performance data from the top of the section:&#x20;

* **All Regions:** Displays performance metrics across all configured regions. &#x20;
* **Individual Regions:** Allows users to focus on the performance metrics for a specific region, such as US East (Ohio), US East (N. Virginia), Canada (Central), etc.&#x20;
* **Multiple Regions:** Allows users to select and view the performance metrics across multiple configured regions.&#x20;

This section enables rapid root cause analysis by identifying which APIs failed and under what load conditions.&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FX7G6Q4nz0zrYyLZWpREY%2FImage%209.png?alt=media&amp;token=31f4a296-2e5d-45ea-ba6b-9a905e3e8ef6" alt=""><figcaption></figcaption></figure>

* **Response Time by API -** Trend graph displaying response times across endpoints, with selectable metrics such as Average, P90, P95, P99, Minimum, and Maximum, enabling detailed percentile-based performance analysis.
* **Throughput by API -** Trend graph showing the throughput (processing rate) per endpoint, enabling visibility into request volume distribution and endpoint-level load patterns over time.

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FedRHnESlqxy9Zx8Qnk2H%2FImage%2010.png?alt=media&amp;token=f8a9fd46-be58-4dac-bc9c-7bc615dfca49" alt=""><figcaption></figcaption></figure>

* **API Response Time Distribution -** Breakdown by latency buckets across API endpoints.&#x20;
* **HTTP Response Codes -** Visual distribution of status codes (e.g., 200, 400, 500).&#x20;

#### Performance Summary Table&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FLr430OPyezcCchvDNrRj%2FImage%202.png?alt=media&amp;token=f9cf1933-6a61-4c36-908a-68a26c8b00cb" alt=""><figcaption></figcaption></figure>

The Performance Summary Table provides a consolidated view of performance metrics for each API or transaction executed during the load test. It enables teams to quickly compare behavior across endpoints and identify bottlenecks or failure patterns. &#x20;

* **Sample Name:** Identifies the specific API or transaction executed during the test.&#x20;
* **Total Requests:** Displays the total number of requests processed for the given sample.&#x20;
* **Failed Requests:** Indicates the number of requests that resulted in errors or unsuccessful responses.&#x20;
* **Average Response Time:** Shows the mean response time across all requests for the sample.&#x20;
* **Minimum Response Time:** Displays the fastest recorded response time.&#x20;
* **Maximum Response Time:** Displays the slowest recorded response time observed.&#x20;
* **P90 Response Time:** Represents the 90th percentile latency, indicating the response time under which 90% of requests were completed.&#x20;
* **Error Rate (%):** Shows the percentage of failed requests relative to total requests.&#x20;
* **Throughput:** Indicates the processing rate, typically measured as requests per second for the given sample.&#x20;

The table supports advanced filtering to refine analysis:&#x20;

* **Transactions/APIs Filter -** Users can toggle between viewing transaction-level metrics or API-level metrics.

### 4. Error Summary&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FvxAluXKwcUcs2QfjRXIu%2FImage%203.png?alt=media&amp;token=7c318eb3-922a-4b26-b6ef-8d598bc846c9" alt=""><figcaption></figcaption></figure>

The Error Summary tab focuses on failure diagnostics:&#x20;

* **Error Count by Status Code -** Time-based visualization of 4xx and 5xx errors.&#x20;
* **Error Rate vs Active Users -** Correlation between load intensity and failures.&#x20;
* **Error Statistics Table -** Breakdown of error types (for eg. Bad Request, Unauthorized, Internal Server Error etc.).&#x20;
* **Error Summary by Sampler -** Endpoint-level failure breakdown across status codes.&#x20;

**Region-Based Selection Filter** &#x20;

When multiple regions are configured for the load test, users can select the **region** for which they want to view performance data from the top of the section:&#x20;

* **All Regions:** Displays performance metrics across all configured regions. &#x20;
* **Individual Regions:** Allows users to focus on the performance metrics for a specific region, such as US East (Ohio), US East (N. Virginia), Canada (Central), etc.&#x20;
* **Multiple Regions:** Allows users to select and view the performance metrics across multiple configured regions.&#x20;

This section enables rapid root cause analysis by identifying which APIs failed and under what load conditions.&#x20;

### 5. Resources&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2F9QPPS7iwXPs5aJRs0sxp%2FImage%204.png?alt=media&amp;token=d7213bc6-c8d7-4d27-86d3-7b41b332e1f2" alt=""><figcaption></figcaption></figure>

The Resources tab monitors infrastructure-level metrics of the load generators:&#x20;

* CPU Usage&#x20;
* Memory Usage&#x20;
* Network Traffic&#x20;
* Disk Usage&#x20;

These metrics help determine whether performance degradation originates from the application under test or from load generator resource constraints.&#x20;

### 6. Regional Performance

{% hint style="info" %}
This section is applicable only when multiple regions are configured for the load test.
{% endhint %}

The Regional Performance section provides a **region-wise view of load test performance**, allowing users to analyze how individual transactions perform across the configured load-testing regions.

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FAZ9aUA8Y2rVyhg3M9LqG%2FRegional%20Performance%201%201.png?alt=media&amp;token=a7f5d56c-8273-4631-8f46-8f9aa02bce8d" alt=""><figcaption></figcaption></figure>

#### Region-Based Selection Filter &#x20;

At the top of the section, users can select the **region** for which they want to view performance data:&#x20;

* **All Regions:** Displays performance metrics across all configured regions. &#x20;
* **Individual Regions:** Allows users to focus on the performance metrics for a specific region, such as US East (Ohio), US East (N. Virginia), Canada (Central), etc.&#x20;
* **Multiple Regions:** Allows users to select and view the performance metrics across multiple configured regions.&#x20;

#### Region-Based Performance Chart&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FxnNd22bWAlLgMl4Y1bCL%2FRegional%20Performance%202%201.png?alt=media&amp;token=1afc43a8-b0af-471d-991d-be07e7ec950f" alt=""><figcaption></figcaption></figure>

The region-based performance chart allows users to **analyze specific APIs** **and transactions** and select the performance metric they want to visualize.&#x20;

* **Transaction Selection:** Users can select one or more APIs / transactions (maximum 5 selections) from the dropdown. The dropdown also provides a search option to quickly find a specific transaction.&#x20;
* **Performance Metrics:** Various performance metrics can be visualized using the region-based performance chart, including:&#x20;

  * **Average Response Time:** Average time taken to process requests. &#x20;
  * **Throughput:** Number of requests/transactions processed over time. &#x20;
  * **Minimum Response Time:** Lowest response time recorded. &#x20;
  * **Maximum Response Time:** Highest response time recorded. &#x20;
  * **Error Count:** Number of errors recorded during execution. &#x20;
  * **P90 Response Time:** Response time below which 90% of requests were completed. &#x20;

  The chart plots the selected metric against elapsed time, providing a time-based view of performance for the selected region(s) and transaction(s).&#x20;

#### Region-Based Performance Comparison Table&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FIZ5Zc2P3At0ljGaUJVnE%2FRegional%20Performance%203%201.png?alt=media&amp;token=2bd887ef-fb63-4ffe-b0a0-ceabed45dd62" alt=""><figcaption></figcaption></figure>

Below the chart, the region-based performance comparison section provides a tabular breakdown of performance by API/Transaction.&#x20;

The table includes the following metrics against each API/Transaction:&#x20;

* **Average Response Time** &#x20;
* **Throughput** &#x20;
* **Minimum Response Time** &#x20;
* **Maximum Response Time** &#x20;
* **Error Rate (%)** &#x20;
* **P90 Response Time** &#x20;

Users can also:&#x20;

* **Search the API/Transaction Name** to locate a specific transaction. &#x20;
* Use the **Metrics Selection** option to control the metrics displayed in the table. &#x20;
* Expand the overall performance metrics to view region-based trends for each api /transaction.&#x20;

Regional Performance helps users compare and analyze **API/transaction-level performance across different regions**, making it easier to identify regional variations in response time, throughput, and errors during a load test.&#x20;

### 7. Timeline Report

The Timeline Report provides a chronological view of test execution. It enables users to create customized charts, add and compare metrics based on their requirements, and analyze client-side metrics region-wise when multiple regions are configured. When APM integrations are configured, users can also view and analyze selected server-side metrics alongside the client-side metrics.

#### Region-Based Visualization of Client-Side Metrics&#x20;

The Timeline Report supports region-based visualization of client-side metrics, allowing you to analyze performance metrics separately for each configured load-testing region. Metrics can be expanded by API or transaction and filtered by region. &#x20;

You can select All Region to view the aggregated metric across all regions or select individual regions to compare regional performance. This enables you to identify differences in client-side metrics across regions and analyze the test performance.&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FjBNaYNpy0cduOg6vhaXK%2F43%201.png?alt=media&amp;token=be2dda1b-c389-472f-923e-0680c0f2dcd0" alt=""><figcaption></figcaption></figure>

#### APM Server-Side Metrics Visualization&#x20;

When APM integrations are configured for a test, PerfAgents automatically collects the selected server-side metrics and displays them alongside load testing results. This allows teams to correlate application behavior with infrastructure resource utilization throughout the duration of the test.&#x20;

The Timeline Report displays the selected infrastructure metrics as interactive charts, for example:&#x20;

* CPU Utilization&#x20;
* Memory Usage&#x20;
* Network In&#x20;
* Network Out&#x20;
* Disk Operations&#x20;
* Custom platform-specific metrics&#x20;

These metrics are plotted across the test execution timeline, allowing users to observe resource behavior under varying load conditions.&#x20;

#### APM Profile Information&#x20;

For tests configured with APM monitoring, the Timeline Report displays:&#x20;

* Associated APM profiles&#x20;
* Integration status&#x20;
* Selected resources&#x20;
* Monitored metrics&#x20;

This provides visibility into the infrastructure components being monitored during the test.&#x20;

#### Comparing Client-Side and Server-Side Metrics&#x20;

By viewing application and infrastructure metrics together, users can quickly identify performance bottlenecks and determine whether issues originate from the application layer or the underlying infrastructure. For example:&#x20;

* Increased response times accompanied by high CPU utilization may indicate server-side processing constraints.&#x20;
* Elevated error rates with stable infrastructure metrics may suggest application-level issues.&#x20;
* Throughput degradation combined with network saturation may indicate bandwidth limitations.&#x20;

#### Interactive Chart Controls&#x20;

Each metric visualization supports additional analysis features, including:&#x20;

* Add charts&#x20;
* Duplicate existing charts&#x20;
* Delete charts&#x20;
* Download charts as images&#x20;

These capabilities allow users to customize the report view and export visualizations for troubleshooting, collaboration, and reporting purposes.&#x20;

#### Real-Time Analysis&#x20;

During test execution, the Timeline Report updates continuously as new monitoring data becomes available. This enables teams to observe performance trends in real time and identify anomalies without waiting for test completion.&#x20;

The Timeline Report serves as a centralized analysis workspace, combining load testing results and infrastructure monitoring data to provide a comprehensive understanding of system performance under load.&#x20;

### 8. UI Performance

{% hint style="info" %}
This section is applicable only when UI Automation is enabled.
{% endhint %}

When UI automation is orchestrated alongside load testing, the dashboard includes a UI Performance tab featuring:&#x20;

#### **Web Vitals**&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2F3UGaE94T9FtPZ1cheJxY%2FImage%205.png?alt=media&amp;token=6b4a013c-2b92-4ab8-bd18-5db02405bc5c" alt=""><figcaption></figcaption></figure>

* **LCP (Largest Contentful Paint) -** Measures the time taken for the largest visible content element (such as an image or heading) to fully render in the viewport.&#x20;
* **INP (Interaction to Next Paint) -** Measures the latency between a user interaction (click, tap, keypress) and the next visual update on the screen.&#x20;
* **CLS (Cumulative Layout Shift) -** Quantifies the visual stability of a page by measuring unexpected layout shifts during loading.&#x20;
* **FCP (First Contentful Paint) -** Indicates when the first piece of content (text, image, canvas, etc.) becomes visible to the user.&#x20;
* **TTI (Time to Interactive) -** Represents the time required for the page to become fully interactive and responsive to user input.&#x20;

#### **Overall Performance Summary**&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FDV33JjykjvscuSvcwu27%2FImage%206.png?alt=media&amp;token=d10c5648-47cf-4254-a20d-0c08b0d6043d" alt=""><figcaption></figcaption></figure>

The Overall UI Performance Summary Table presents a transaction-level breakdown of critical UI flows executed during the test. It provides detailed latency metrics for each UI transaction, including:&#x20;

1. **Transaction Name:** The name assigned to the transaction.&#x20;
2. **Average Time -** Mean execution time across iterations.&#x20;
3. **90th Percentile Time -** Time within which 90% of executions were completed, highlighting tail latency.&#x20;
4. **Standard Deviation -** Variability in execution time, indicating consistency.&#x20;
5. **Minimum Time -** Fastest observed execution.&#x20;
6. **Maximum Time -** Slowest observed execution.&#x20;

This table enables teams to identify slow or unstable UI transactions under load and correlate them with backend performance behavior.&#x20;

#### **Execution Iterations & Artifacts includes:**&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FlfWKhTLYxk7jU1qMmpbs%2FImage%207.png?alt=media&amp;token=0bc1a0af-120f-4795-aae1-7ce80863f24e" alt=""><figcaption></figcaption></figure>

* Iteration Status (Completed / Failed) and Triggered Time&#x20;
* Transaction-Level Timings&#x20;
* Console Logs&#x20;
* Playwright Traces&#x20;
* Video Recordings & Screenshots&#x20;

This ensures full traceability of user journey validation under load.&#x20;

### 9. Logs&#x20;

<figure><img src="https://745121973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM3G6DqjCMUX4UCZW0v1H%2Fuploads%2FDvDa8UfnAj0Nwp9LYtyl%2FImage%208.png?alt=media&amp;token=ebd62434-a756-484e-a38c-743ce7a925bb" alt=""><figcaption></figcaption></figure>

The Logs section provides detailed execution-level visibility into the load test by displaying real-time **JMeter** **logs** generated during the test run. It captures system-level and script-level events such as environment initialization, configuration loading, JVM settings, property assignments, execution context details, and runtime information for controller and worker nodes. Users can switch between different nodes (e.g., Controller or Worker instances) to inspect distributed execution logs, making it easier to troubleshoot failures and validate configuration settings.&#x20;

#### Export Options&#x20;

Test results can be downloaded as:&#x20;

* Result CSV&#x20;
* HTML Report (ZIP)&#x20;

These exports allow offline analysis and reporting.&#x20;

### Purpose of the Real-Time Dashboard&#x20;

The Real-Time Load Test Dashboard enables teams to:&#x20;

* Monitor load test execution live.&#x20;
* Identify performance bottlenecks instantly.&#x20;
* Correlate backend metrics with UI performance (if enabled).&#x20;
* Analyze errors with endpoint-level granularity.&#x20;
* Validate infrastructure resource utilization.&#x20;
* Perform deep debugging using logs and traces.&#x20;

It provides a unified, actionable view of system behavior under stress-bridging load generation, application performance, and user experience validation within a single analytical interface.&#x20;


# Load Test Dashboard

The Load Test Dashboard provides a centralized view of all load testing activities within a selected project. It gives instant visibility into test executions, system performance trends, and infrastructure utilization. This dashboard is accessible via the Dashboard section. It updates dynamically based on the selected organization, project, and time range (e.g., Last 7 Days).&#x20;

{% embed url="<https://youtu.be/WrQkk2BLHaI>" %}

### Layout Structure&#x20;

The Load Testing Dashboard consists of:&#x20;

1. Summary Metric Cards (Top Section)&#x20;
2. Top Load Tests List&#x20;
3. Recent Runs&#x20;
4. Test Activity Graph&#x20;
5. Test Run Count Graph&#x20;
6. Time Range Filter&#x20;

### Summary Metrics (Top Section)&#x20;

The top row displays high-level KPIs for quick performance insights:&#x20;

<table><thead><tr><th width="214.6900634765625">Metric</th><th width="269.5">Description</th><th>Purpose</th></tr></thead><tbody><tr><td>Active Test </td><td>Number of currently running tests vs. completed tests. </td><td>Helps identify whether load tests are actively executing. </td></tr><tr><td>Total Runs (Last 7 Days) </td><td>Total number of test executions during the selected time period. </td><td>Tracks testing frequency and adoption trends. </td></tr><tr><td>Failed Load Tests </td><td>Number of failed executions. </td><td>Provides immediate visibility into stability and execution health. </td></tr><tr><td>Total LG-Hours </td><td>Virtual User (VU) consumption and percentage of allocated capacity used. </td><td>Tracks plan usage and resource efficiency. </td></tr><tr><td>Average Completion Rate </td><td>Average success rate across executed tests. </td><td>Helps measure overall reliability of test executions. </td></tr></tbody></table>

### Top Load Tests List & Recent Runs&#x20;

These panels highlight the most frequently executed tests and the most recent executions, providing a quick snapshot of current performance activity.&#x20;

#### Test Activity & Run Count Graphs&#x20;

These visual trend charts display:&#x20;

1. **Test Activity Graph:** Daily test runs and Success Rate over time, helping to assess if reliability is improving or declining.&#x20;
2. **Test Run Count Graph:** Historical view of test frequency and operational discipline.&#x20;

### Time Range Filter&#x20;

Located in the top-right, this filter allows users to adjust the time range (default: Last 7 Days) to analyze weekly or monthly trends.&#x20;

### How to Use This Dashboard Effectively&#x20;

The Load Testing Dashboard is designed for:&#x20;

1. **Engineering Teams:** To track execution frequency and identify test failures.&#x20;
2. **Performance Teams:** To evaluate load test stability and monitor VU utilization.&#x20;
3. **Leadership / Stakeholders:** To get a high-level snapshot of testing activity and assess reliability trends.


# Synthetic Monitoring

The Synthetic Monitoring section helps you continuously track the availability and performance of your applications using automated checks. It explains how different types of monitors are created, executed, and observed over time, ensuring early detection of failures and performance degradation.

{% stepper %}
{% step %}

### Create Monitoring

This subsection explains how to create synthetic monitors in PerfAgents. It covers monitor types such as Website, REST API, and Sequence monitoring, along with basic configuration requirements.
{% endstep %}

{% step %}

### Website Monitoring

Website monitoring allows you to continuously check the availability and response behavior of a web application. This subsection covers how website monitors are created, configured, and executed at regular intervals to validate uptime and basic performance.
{% endstep %}

{% step %}

### REST API Monitoring

REST API monitoring enables automated checks for API endpoints. This section explains how API monitors validate response status, latency, and correctness, helping ensure backend services remain reliable and responsive.
{% endstep %}

{% step %}

### Sequence Monitoring

Sequence monitoring is used to validate multi-step user flows. This subsection explains how a series of dependent requests are executed in order, ensuring that complete workflows function as expected from start to finish.
{% endstep %}

{% step %}

### Monitoring Results & Status

This section explains how monitoring outcomes are displayed. It covers execution status, success and failure indicators, response metrics, and historical monitoring data for analysis and troubleshooting.
{% endstep %}
{% endstepper %}


# Setup Monitoring

Monitoring in PerfAgents is the practice of performing continuous, low-volume checks on your application's endpoints and user flows from various global locations. Unlike load testing, which is run on demand to test scalability, monitoring runs on a schedule to sustain reliability and detect issues like downtime, performance degradation, or certificate expiry in real-time.&#x20;

### Understanding Types of Monitoring&#x20;

PerfAgents supports three distinct types of synthetic monitoring, allowing you to cover everything from basic availability to complex user interactions:&#x20;

<table><thead><tr><th width="106.79510498046875">Type</th><th width="341.6666259765625">Purpose</th><th>Focus</th></tr></thead><tbody><tr><td>Website </td><td>Checks the availability and performance of a single URL. </td><td>Uptime, response time, SSL validity. </td></tr><tr><td>REST API </td><td>Checks the performance and correctness of API endpoints. </td><td>API response, data validation (assertions), multi-step chaining. </td></tr><tr><td>Sequence </td><td>Simulates multi-step user flows (e.g., login, search, checkout). </td><td>End-to-end user experience validation. </td></tr></tbody></table>

### Create Your First Monitoring (Website)&#x20;

{% embed url="<https://youtu.be/vSIUQmh53mE>" %}

This guide walks you through setting up a basic Website monitor, which is ideal for tracking the uptime and performance of a single URL.&#x20;

Navigate to: Monitoring → Create Monitoring&#x20;

The setup is a 4-step guided flow:&#x20;

#### Step 1: Type Selection&#x20;

Select Website as the monitoring type.&#x20;

#### Step 2: Configurations&#x20;

1. **Monitoring Name:** Provide a descriptive name (e.g., Homepage Uptime Monitor).&#x20;
2. **Tags (Optional):** Add metadata for filtering (e.g., production, critical).&#x20;
3. **Endpoint Configuration:**&#x20;
   1. **Method:** GET is selected by default for Website Monitoring.&#x20;
   2. **URL:** Enter the target endpoint (e.g., <https://example.com).&#x20>;
4. **SSL Certificate Monitoring (Optional):** Enable this to monitor SSL expiration and trigger alerts before the certificate expires.&#x20;
5. **Advanced Configuration:** Use the tabs for Params, Authorization (Basic Auth, Bearer Token), and Headers if required.&#x20;

#### Step 3: Frequency&#x20;

Define how often the monitor runs (e.g., Every 1 minute, Every 5 minutes). Higher frequency allows for faster issue detection.&#x20;

#### Step 4: Alerts & Notifications&#x20;

**Use Global Alert Rules:** Enable this to apply organization-level alert settings.&#x20;

**Integrations:** Configure where alerts should be sent. Available integrations include Email, AWS SNS, Jira, Linear, Microsoft Teams, PagerDuty, Slack, Splunk, and Webhook.&#x20;

#### Final Step: Create Monitor&#x20;

Click Create. Your monitor will now execute automatically at the defined intervals, log response data, and trigger alerts when thresholds are breached.&#x20;

### Create Your First Monitoring (REST API)&#x20;

{% embed url="<https://youtu.be/p96E7tfu_xs>" %}

REST API Monitoring allows you to continuously validate the availability, performance, and correctness of your APIs. It ensures endpoints respond as expected and meet defined response criteria.&#x20;

#### Step 1: Type Selection&#x20;

Select REST API - Monitor APIs as the monitoring type. This option is used to test single or multi-step API endpoints.&#x20;

#### Step 2: Configurations&#x20;

1. **Basic Details:** Provide the Monitoring Name and optional Tags.&#x20;
2. **Endpoints Configuration:** Each API monitor can include one or more endpoints.&#x20;
   1. **Endpoint Settings:** Define the HTTP Method (GET, POST, PUT, etc.), Protocol (HTTP/HTTPS), and the URL.&#x20;
   2. **Multi-Step Toggle:** Enable this to chain API calls, allowing you to pass data (e.g., tokens) between steps.&#x20;
3. **Request Configuration Tabs:** Each endpoint supports detailed configuration:&#x20;
4. **Params:** Add Query Parameters (Key–Value pairs).&#x20;
5. **Body:** Define the request payload (for POST/PUT methods).&#x20;
6. **Authorization:** Supports authentication types such as API Keys, Bearer Tokens, and Basic Auth.&#x20;
7. **Headers:** Add custom request headers.&#x20;
8. **Assertions:** Define validation rules such as Status code checks, Response body validation, JSON path assertions, and Response time thresholds.&#x20;

#### Step 3 & 4: Frequency and Alerts&#x20;

These steps are identical to the Website Monitoring setup, allowing you to define the monitoring interval and configure your Alerts & Notifications via integrations like Slack, Jira, and Email.&#x20;

### Create Your First Monitoring (Sequence)&#x20;

{% embed url="<https://youtu.be/7ZTfmODEEQk>" %}

Sequence Monitoring is designed for browser-based user journey monitoring. It simulates real user flows across multiple pages or actions, making it ideal for validating critical workflows like login, checkout, or form submissions.&#x20;

#### Step 1: Type Selection&#x20;

Select Sequence Monitor Browser Flows as the monitoring type.&#x20;

#### Step 2: Configurations&#x20;

1. **Basic Details:** Provide the Monitoring Name and optional Tags.&#x20;
2. **Select Framework:** Choose the automation framework used to execute the sequence: Playwright, Selenium, Puppeteer, or Cypress.&#x20;
3. **Script Options:** \
   Configure your script as follows:&#x20;
   1. Import Script: Upload your existing test scripts.&#x20;
   2. Generate with AI (Beta): Auto-generate script logic.&#x20;
   3. Create Script: Manually create a new test script.&#x20;
   4. You can also upload Dependencies and required supporting files.&#x20;
4. Device Configuration:  \
   Simulate the monitoring environment:&#x20;
   1. **Browser Type:** Choose between Chromium or WebKit.&#x20;
   2. **Device Resolution**: Set the resolution (e.g., 1920 × 1080) to ensure consistent UI validation.&#x20;

#### Step 3 & 4: Frequency and Alerts&#x20;

These steps are identical to the other monitoring types. Alerts can trigger Script failure, Assertion failure, Timeout, or Performance threshold breach.&#x20;


# Monitoring Dashboard

The Monitoring Dashboard provides a high-level summary and operational health view of all monitors within the selected project.&#x20;

{% embed url="<https://youtu.be/ezUF0fPM4Zg>" %}

### Key Dashboard Metrics&#x20;

The dashboard displays critical performance indicators for quick assessment:&#x20;

<table><thead><tr><th width="218.70050048828125">Metric</th><th width="279.920166015625">Description</th><th>Purpose</th></tr></thead><tbody><tr><td>Total Monitors </td><td>Total number of configured monitors. </td><td>Tracks monitoring coverage. </td></tr><tr><td>Monitoring by Type </td><td>Distribution across Website, REST API, and Sequence. </td><td>Helps understand system coverage. </td></tr><tr><td>Availability (Average) </td><td>Overall uptime percentage across all monitors. </td><td>Primary measure of system health. </td></tr><tr><td>Response Time (Average) </td><td>Average response time across all monitors. </td><td>Primary measure of system performance. </td></tr><tr><td>Open Alerts </td><td>Number of current active alerts. </td><td>Quick health signal for operational teams. </td></tr><tr><td>Global Monitoring Map </td><td>Visually represents the geographic locations from which monitoring checks are executed. </td><td>Tracks global availability and coverage footprint. </td></tr></tbody></table>