Watch Logs not displaying logs from simulation, and the logs from successful runs


I have a simulation running in Gatling Enterprise. The version is 1.16.4 with Gatling Version 3.7.6.FL.

Generally, I’d like to see the logs of additional information for the class initialization before starting the injection.

There is a logback.xml in src/main/resources:

<?xml version="1.0" encoding="UTF-8" ?>
<configuration debug="true">
    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
            <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
    <root level="INFO">
        <appender-ref ref="STDOUT"/>

And the logger is initialized as:

class RequestSimulation extends Simulation {
    private val logger = LoggerFactory.getLogger(classOf[RequestSimulation])"Starting ${classOf[RequestSimulation]}")

This works well when I run the simulation locally using Gatling.fromMap(

However, in Gatling Enterprise - Watch Logs, I only see the following information. It looks like the logs from the logger of simulation are not redirected to the web UI.

[10:24:14,014]  Starting a Gradle Daemon (subsequent builds will be faster)
[10:24:18,014]  > Task :buildSrc:compileJava
[10:24:18,015]  > Task :buildSrc:compileGroovy NO-SOURCE
[10:24:18,113]  > Task :buildSrc:processResources
[10:24:18,113]  > Task :buildSrc:classes
[10:24:18,113]  > Task :buildSrc:jar
[10:24:18,113]  > Task :buildSrc:assemble
[10:24:18,114]  > Task :buildSrc:compileTestJava NO-SOURCE
[10:24:18,114]  > Task :buildSrc:compileTestGroovy NO-SOURCE
[10:24:18,114]  > Task :buildSrc:processTestResources NO-SOURCE
[10:24:18,114]  > Task :buildSrc:testClasses UP-TO-DATE
[10:24:18,114]  > Task :buildSrc:test NO-SOURCE
[10:24:18,114]  > Task :buildSrc:check UP-TO-DATE
[10:24:18,114]  > Task :buildSrc:build
[10:24:18,713]  > Task :clean UP-TO-DATE
[10:24:18,713]  > Task :compileJava NO-SOURCE
[10:24:20,713]  > Task :compileScala
[10:24:20,713]  Pruning sources from previous analysis, due to incompatible CompileSetup.
[10:24:24,713]  > Task :processResources
[10:24:24,714]  > Task :classes
[10:24:31,413]  > Task :shadowJar
[10:24:31,413]  BUILD SUCCESSFUL in 17s
[10:24:31,414]  4 actionable tasks: 3 executed, 1 up-to-date
[10:24:32,010]  Compilation completed successfully.
[10:24:32,012]  Collected jars (/tmp/frontline-8598110199430405754/buildSrc/build/libs/buildSrc.jar, /tmp/frontline-8598110199430405754/build/libs/loadtest-bidrequest.jar)
[10:24:32,014]  WARNING!!!: Could not detect Gatling version and verify compatibility, assuming Gatling 3.3. Please upgrade maven/gradle/sbt Gatling Enterprise plugin to latest version and Gatling to 3.7
[10:24:32,014]  Packages successfully collected and instances successfully spawned. Proceeding with ssh checks.
[10:24:33,294]  Connected over ssh to DA1/
[10:24:33,294]  All instances could be connected over ssh. Proceeding with Upload.
[10:24:43,647]  All uploads to DA1/ successful.
[10:24:43,647]  All uploads successful. Proceeding with instance checking.
[10:24:44,978]  Instance DA1/ check successful.
[10:24:44,978]  All instances check successful. Proceeding with booting injectors.
[10:24:46,265]  Injector on instance DA1/ successfully booted.
[10:24:46,265]  All injectors successfully booted.
[10:24:46,372]  Couldn't connect over HTTP to DA1/ on port 9999: j.n.ConnectException: Connection refused (Connection refused). 9 remaining tries, please wait.
[10:24:47,494]  Couldn't connect over HTTP to DA1/ on port 9999: j.n.ConnectException: Connection refused (Connection refused). 8 remaining tries, please wait.
[10:24:48,807]  Connected over HTTP to DA1/
[10:24:48,807]  All instances could be connected over HTTP. Proceeding with fetching Simulation boot info.
[10:24:48,929]  Couldn't fetch Simulation info from DA1/ Simulation is not instantiated yet. 599 remaining tries, please wait.
[10:25:38,220]  Fetched Simulation info from DA1/
[10:25:38,220]  Simulation info could be fetched from all instances. Proceeding with starting.
[10:25:38,334]  Injector DA1/ successfully started.
[10:25:38,334]  All injectors could be started. Proceeding with Running.
[10:25:38,334]  Run 2c4df146-7ff5-49d4-8df2-3aa5402c58f7: starting injection
[10:26:29,464]  Run 2c4df146-7ff5-49d4-8df2-3aa5402c58f7: successful, terminating

Do you know how can I have these logs from UI? Is there a setting in Gatling Enterprise or am I doing wrong in my local configuration?

Another question: if a run is successful, the “Watch logs” icon will disappear, then I cannot find the run logs anymore. Is it possible to find the logs of these successful runs?


Thanks for getting in touch. On the Enterprise version we don’t actually have access to these logs because of the amount of requests it’s possible to make and storing all of these could quickly fill up databases and cause issues, we’re looking at providing some samples of errors in a future edition but don’t have an ETA on when this will be available.

Regarding the logs for the successful runs, we don’t provide access to those as there is really nothing to show (just injectors being initialized, etc.) for a successful run. We display them for failed or broken runs so they can help you debug but for successful runs they don’t really provide any value.

As a note for future issues you can contact me to give you access to the Enterprise Support Portal for resolution of Enterprise issues.

All the best,


Thanks for the reply. As all the custom logs are not redirected, there’s indeed no big value to show the successful runs. In this case, I’ll need to retrieve these logs from the simulation class by other methods.

How can I request access to the Enterprise Support Portal?