HTTP: Whole traffic from WebSocket is logged as a DEBUG - can't filter failed messages #4468
Description
Hello,
I'm using Gatling 3.9.5 and found that issue reported here: #4439 is still visible. Original ticket was not reopened so I raised another one
During simulation with WebSocket every log related to WebSocket traffic is using DEBUG level. It means even if I try to log to file only failed messages Gatling will store everything. The most annoying issue of that is a log file with a couple of GBs which is harder to store/parse after tests
Is it possible to fix this and use logic similar to HTTP where using DEBUG for logging only failed messages will be logged, and TRACE for everything?
My logback.xml content:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss.SSS} [%-5level] %logger{15} - %msg%n%rEx</pattern>
</encoder>
<immediateFlush>false</immediateFlush>
</appender>
<appender name="FILE" class="ch.qos.logback.core.FileAppender">
<file>target/gatling/LastRun.log</file>
<append>true</append>
<encoder>
<pattern>%d{HH:mm:ss.SSS} [%-5level] %logger{15} - %msg%n%rEx</pattern>
</encoder>
</appender>
<!-- uncomment and set to DEBUG to log all failing HTTP requests -->
<!-- uncomment and set to TRACE to log all HTTP requests -->
<logger name="io.gatling.http.engine.response" level="DEBUG"/>
<logger name="io.gatling.http.action.ws.fsm" level="DEBUG" />
<root level="WARN">
<appender-ref ref="FILE"/>
<!-- <appender-ref ref="CONSOLE"/>-->
</root>
</configuration>
BR
Mateusz