I'm sure this is OS dependent as well. I've only seen the obvious: if you log a ton of data, say at the DEBUG level, and enable DEBUG, then yeah, things are going to slow down. Obvious.
The complain I usually hear is that our server logs too much DEBUG data, and that users do not know which log category to disable to alleviate this issue. But that is not a Log4j issue. Gary On Mon, Apr 2, 2018 at 10:29 AM, Ralph Goers <[email protected]> wrote: > Some of my team members at work are looking to move some services into > Docker containers managed by Kubernetes following the guidance at > https://12factor.net/logs <https://12factor.net/logs>. > > We have guidance that shows writing to the console is terrible and I > remember having a discussion that writing to stdout is bad even if it is > redirected to a file, but I can’t seem to find a link to that. > > Do any of you have experience with this? My gut instinct is telling me > that what they are trying to do is a horrible idea. > > Ralph
