4 ms·
“the difference between a 20 hour journey through a code base and a short stop to immediately discovering the problem.” I had situations where the difference w
by spaetzleesser 5y ago
“the difference between a 20 hour journey through a code base and a short stop to immediately discovering the problem.”
I had situations where the difference was between having an intermittent problem for months or years that nobody can figure out and pouring over logs for days and finding the problem.
I do pretty extensive logging in my code and it has saved my ass many times. Before people complain about performance or storage problems I want to see hard profiling numbers. In most cases you it’s only a few places where the logging is causing problems and you can reduce it there.
Overlogging is almost never a real problem in my experience. You can always discard log data you have but you can’t create log data you may need but didn’t produce.
- outworlder 5y ago> Overlogging is almost never a real problem in my experience I would disagree, after managing a 100 node ELK monstrosity to try to process the terabytes of logs generated by our systems. Overlogging is not a problem if log levels can be easily changed (preferably without an app restart). One app logging like crazy is not a problem. A thousand of microservices, is.