Skip to content
  • ZipCode Api
  • Blog
  • About RedLine13
RedLine13
Primary Navigation Menu
Menu
  • Start Testing
  • Demo
  • Pricing
  • Docs
    • Knowledge Base
    • AWS IAM Setup Instructions
    • Running a RedLine13 Load Test with Advanced Options
    • Scalability
    • Writing Open Load Tests in Your Language
    • Jenkins Plugin Setup
    • AWS Approval for Large Tests
    • Pro Features
  • JMeter
  • Partners

Generating Gatling Reports across multiple servers

By: RedLine13

RedLine13 continues making load testing easier and cheaper than anyone else. We have extended RedLine13 Gatling support to generate Gatling Reports across all of your load agents.  This allows you to take advantage of the RedLine13 generated metrics and full access to the Gatling reports.

You can run your gatling test on 1 – 100 (technically even more) servers and your output will include the cross-agent gatling report.  This is supported for Gatling version 2.1.x or Gatling 2.2.x, executed directly or using our maven execution.

Feature requires enterprise plan.

Generating Reports

  • Follow the standard steps for running a gatling load test
  • Check “Save the response output from individual tests and calculate percentiles”
  • Select # servers and your cloud settings.

The following is a 4 server test ( 2 in Virginia, 2 in Mumbai )

Gatling Load Test 4 servers for reports

Downloading Gatling Reports

After the test completes and finishes its post-processing the output files will be available. The following report is from the aggregated data across all 4 load agents.

Cloud Test Gatling Report Cross Load Agents

Viewing Gatling Report

Once downloaded and expanded just open the index.html in your browser and you will have full access to the Gatling-Reports.

Gatling Downloaded Reports

And you have the full gatling report.

Gatling Report 4 server

RedLine13 Reports

RedLine13 metrics and reports are available for viewing in the web ui.  RedLine13 UI metrics are displayed live during the test and summarized after the test completes.   RedLine13 metrics include dashboard, percentiles, overview, error, agent, and error logs.

Summary

Gatling summary metrics

Metrics

Gatling Request Metrics

Agent Metrics

  • Two servers are m3.medium and two are m4.large. You can see the difference in the CPUs between them.

Gatling Test Agent Metrics

 

2016-07-05
Previous Post: Executing Gatling Test Using Maven
Next Post: Gatling 2.2.X support

Recent Posts

  • Use Cases for the JMeter Dashboard Report
  • AWS Costs for Large JMeter Load Tests Run by Real Customers
  • AWS Multiple Account Setup for Load Testing – Securing your Application Environment
  • Merge Results for Data Analysis
  • Debug your JMeter Test with Output Files

Related

  • SAML SSO
  • E-Learning Companies and Load Testing
  • AWS Multiple Account Setup for Load Testing – Securing your Application Environment
  • AWS Costs for Large JMeter Load Tests Run by Real Customers
  • Why BlazeMeter Customers Chose RedLine13
  • Is BlazeMeter Scared Of RedLine13?
  • RedLine13 Customer HBO Latin America Speaks at Customer Advisory Board Meeting
  • ThinkLogic and High Volume Tests on RedLine13
  • Why ACT Moved from BlazeMeter – Highlights from the RedLine13 Customer Advisory Board Meeting
  • University of California Wanted a LoadRunner Alternative

© RedLine13, LLC | Privacy Policy | Contract
Contact Us: info@redline13.com