There is a dependency between all three modules, which is why the modules should be executed in the following order:
gatling-adapter > gatling-runner > gatling-exporter
The gatling-adapter reads a RQA-Configuration and adapt it to a dqualizer gatling-configuration.
The created gatling-configuration will be written either into the gatling-adapter project or the gatling-runner project.
You can configure the project via the environmental variable GATLING_CONFIG_MODULE.
The gatling-runner provides a Simulation template for gatling load tests. To run load tests, a dqualizer gatling-configuration has to be provided before building the project.
An example for a dqualizer gatling configuration can be found here.
Gatling HTML-reports will be stored in the folder results.
The gatling-exporter uses the simulation.log files from the results folder to create metrics.
These metrics will be exported to an OpenTelemetry-Collector via HTTP.
You can configure the host for the collector via the environmental variable OTEL_HOST.
When running in Docker, it is important to pass specific files from one module to another. You can use the docker-shared folder for this.
The gatling-adapter creates a dq-gatling.conf, which has to be passed to the gatling-runner.
The wait_for_file.sh script will wait until the configuration exists, before starting the jar.
The gatling-runner creates simulation results, which have to be passed to the gatling-exporter.
Additionally, the docker-config folder contains configurations for the OpenTelemetry-Collector as well as Grafana.
All created Metrics will be stored inside a InfluxDB (v2) and can be viewed in Grafana.