Re:Do Not Log
by outworlder on Wednesday January 05, 2022 @12:52PM
(#29812377)
> Also, do overlog. It can be hard or impossible to attach a debugger to the deployed application. But you can always turn the log level up to 11 and then reconstruct what happened from the log messages.
Please don't overlog. Only ever do this if you can dynamically change your log level on demand, without impacting users.
If you do have to reconstruct a sequence of events and you do not have distributed tracing, fine. Log the sequence of events _when needed_.
But please don't log messages on a perfectly fine system for no reason. It's noise and health can be better served by looking at metrics.
Because of this overlogging nonsense our systems generate terabytes of logs daily. Most of it is never ever looked at.
Re:Do Not Log
by fuzzy2 on Wednesday January 05, 2022 @01:32PM
(#29812987)
Well yes of course? That’s what log levels and log categories are for. Whether the configuration can change at runtime or if your services have to cycle doesn’t really matter IMHO.
Please don't overlog. Only ever do this if you can dynamically change your log level on demand, without impacting users.
If you do have to reconstruct a sequence of events and you do not have distributed tracing, fine. Log the sequence of events _when needed_.
But please don't log messages on a perfectly fine system for no reason. It's noise and health can be better served by looking at metrics.
Because of this overlogging nonsense our systems generate terabytes of logs daily. Most of it is never ever looked at.