During tests with Websockets I found that, even if logger: io.gatling.http.action.ws.fsm is set to DEBUG Level all data is logged - every message, every matching response etc
Shouldn’t it write only those messages where check or matching not meet requirements?
Hi,
a little old version of Gatling - consider upgrade.
As is in documentation (Gatling - WebSocket) this logger give possibility to “inspect WebSocket traffic” so I think he do his best giving almost everything
It’s old, but unfortunately at the moment I don’t have time to check if simulation.log format was changed. Im using my own scripts to gather trend from my tests, based on Gatling’s logs but I have it on my backlog to update version to the latest one.
Regarding “inspect WebSocket traffic” - if it’s a proper behaviour worth to add this to documentation. During my tests Im logging only failed requests to a file, so whole traffic from WS is making a mess