Tracing Transactions for Gatling Load Testing

Imagine you’re performing Gatling Load Testing on Flood‘s distributed cloud based infrastructure and your response times start to waver, or worse, your failed rate of requests per minute starts to climb.

You check your Flood charts and they’re demonstrating failures under load.

Previously, as with most other cloud based load testing tools you’d be left wondering, what happened to that request? What was actually returned by the server? You might begin to grep the mountains of logs on your app servers looking for a clue, but wouldn’t it be nice to have Flood show you exactly what was returned from a client point of view?

All Gatling tests run on Flood now have the ability to inspect the slowest successful and failed transaction request and response headers, live, whilst your test is running. In addition, you also have the ability to view request and response data returned by the server for failed transactions. This offers you much better fault finding capability under load.

You don’t have to configure anything else in your test plan. We do this automatically with some innovation inside Gatling and our own reporting engine.

If you’d like to check this out, make sure to sign up for a trial of Flood.  Once you’ve signed up, follow this easy tutorial to get started load testing with Gatling.


Ready to get started?

Sign up or request a demo today.