Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/gatling/gatling.io-doc/llms.txt

Use this file to discover all available pages before exploring further.

Gatling’s plugin architecture allows the community to build protocol support beyond the officially maintained set (HTTP, WebSocket, SSE, gRPC, JMS, MQTT). These community plugins follow the same simulation API patterns you already know, letting you load test message queues, databases, file transfer services, and more. Because these projects are maintained by their respective authors rather than the Gatling core team, stability, update cadence, and Gatling version compatibility vary.
These projects are third-party contributions and are not maintained by the Gatling core team. If you encounter an issue, contact the plugin’s respective owner on GitHub. The Gatling team cannot provide support for third-party plugins.

​
Active Plugins

The following plugins are currently maintained and support recent Gatling versions:

AMQP Plugin

Gatling 3.13 — Load test AMQP brokers (e.g. RabbitMQ). Contributed by jigarkhwar.

SFTP Plugin

Gatling 3.13 — Load test SFTP servers. Contributed by François Herbreteau.

FTP Plugin

Gatling 3.13 — Load test FTP servers. Contributed by François Herbreteau.

JDBC Plugin

Gatling 3.13 — Load test relational databases via JDBC. Contributed by jigarkhwar.

Kafka Plugin

Gatling 3.13 — Load test Apache Kafka topics. Contributed by jigarkhwar. See also the Gatling blog Kafka starter guide.

​
Inactive / Legacy Plugins

The following plugins are no longer actively maintained or are pinned to an older Gatling release. They may still be useful as a reference or starting point if you want to fork and update them.
These projects are stuck on old Gatling versions or are no longer receiving updates. Consider reaching out to their authors on GitHub to help upgrade them, or fork the project for your own use.
PluginLast Known Gatling VersionAuthor
Git plugin3.9GerritForge
gRPC plugin3.9George Leung
Kafka plugin3.9Amerousful (Bairov Pavel)
NATS plugin3.0Logimethods
Neo4j Bolt plugin3.3Stefan Armbruster
Radius plugin3.1Bilal Pierre Abdelkader
The gRPC plugin listed above is a legacy community implementation. Gatling now ships an official first-party gRPC module as part of Gatling Enterprise that should be preferred for new projects.

​
Evaluating a Third-Party Plugin

Before adopting a community plugin, check the following:
1

Check Gatling version compatibility

Confirm the plugin targets the same major/minor Gatling version your project uses. Gatling’s SDK and internal APIs can change between minor versions.
2

Review recent activity

Look at the plugin’s GitHub repository for recent commits, open issues, and pull requests. An inactive repository may not support your target Gatling version.
3

Run the demo or example

Most plugins include a sample simulation. Run it against a local test server to verify the plugin works in your environment before integrating it into a larger test suite.
4

Check the license

Open-source plugins may carry different licenses (MIT, Apache 2, etc.). Verify the license is compatible with your project’s requirements.

​
Publishing Your Own Plugin

If you build a Gatling protocol extension that you’d like to share with the community, consider:
  • Publishing it as an open-source library on Maven Central or a public GitHub repository
  • Following the existing plugin naming convention (gatling-<protocol>)
  • Including a demo project and a README that documents Gatling version compatibility
  • Posting about it in the Gatling Community Forum so others can discover it

Build docs developers (and LLMs) love

Get started for freeTalk to us