As the title says, I bumped into a case that we sometimes need to kill the Gatling process because it affects another simultaneous running test against the target system. And we have to kill all tests but still want to review how Gatling simulation runs before we kill it.
However, seems Gatling only flush content to simulation.log when the script runs all the way till the end successfully.
So, is there a way to force Gatling flush the log even it’s killed? Or we can intercept the log from elsewhere?