The simulation log file is not UTF-8 encoded

Gatling (Open-Source)
1

Gatling version: 3.13.1 (must be up to date)
Gatling flavor: [ X] java kotlin scala javascript typescript
Gatling build tool: [ X] maven gradle sbt bundle npm

I read the guidelines and how to ask a question topics.
I copied output I observe, and explain what I think should be.

Hello everyone,

I am encountering an issue where the simulation.log file generated by Gatling is not encoded in UTF-8 as expected. From my understanding, Gatling’s default encoding is UTF-8, but for some reason, the output file seems to have a different encoding.

Here are the details of my setup:

  • Gatling Version: [3.13.1]
  • Java Version: [11.0.24]
  • Operating System: [e.g., Windows/Linux]
  • Configuration: The gatling.conf file has not been modified, so it should still be using the default encoding.

I’ve tried the following to troubleshoot:

  1. Checked the encoding of the simulation.log file using tools like file (on Linux) and found it’s not UTF-8.
  2. Explicitly set gatling.core.encoding = "UTF-8" in the gatling.conf file.
  3. Ran Gatling with -Dfile.encoding=UTF-8 as a JVM argument.

Despite these attempts, the issue persists. Has anyone else faced a similar problem or know what might be causing this? Could it be related to system locale settings or Java configuration?

Any advice or guidance would be greatly appreciated!

Thank you in advance.

2

Hello,

Indeed, the format of this file is not UTF-8. And it shouldn’t be a concern to you.
As explained in our FAQ, the simulation.log file is an internal.

If your problem is that some of your characters get mangled in the HTML reports we generate, then it’s a bug. In this case, please provide a reproducer we can use to investigate.

Otherwise, I guess you’re trying to do something that’s not supported. In this case, I recommend you don’t.

3

Hi Yu79,

yes we are facing the same issue as you do, I also opened a thread of the implications here: