A Brief Introduction to Simulation Reporting

The simulation metrics gathered in measurements can be written into simulation log files. So as to enable simulation logging, you need to add @Logging annotation to the class:

@Simulation(name = "Server-Status Simulation")
@Logging(file = "/var/log/simulation.log", formatter = GatlingLogFormatter.class)
public class PerformanceTestingExample {
  
}

Formatter attribute specify the format of the log file you want to use. The framework supports Gatling simulation file format with GatlingLogFormatter, so that the Gatling simulation reports can be generated by using Gatling tooling. You can omit the formatter parameter to employ the default formatting. In addition, you can write your own formatter by implementing the LogFormatter interface and develop your own tooling to create simulation reports.

Moreover, during the load testing run, Rhino will also report the report into the stdout to show his heartbeat:

    .-.__O\
     `Y     `-.
      )   ,
  |`-\`  (@   )    Rhino 1.1.2.RELEASE Load and Performance Testing
   \_.   `  /`     http://ryos.io
   (   >_ .` `\
    \__//‘     `

-
Starting load test for 5 minutes ...
Preparation in progress.
Number of users logged in : 2
Tests started : 20:45:35
Elapsed : 1 secs ETA : 20:50:35 (duration 5 mins)
==========================================================================
-- Number of executions --------------------------------------------------
> Discovery        Discovery                             200 2
-- Response Time ---------------------------------------------------------
> Discovery        Discovery                             200 12 ms

==========================================================================
                             Average Response Time        12 ms
                                     Total Request         2 
==========================================================================