33 ms·
"You never know when you might need this info to debug" The developer says as their cronjob creates a 250MB csv file, and a few MB of debug logs per day, for th
by briffle 5y ago
"You never know when you might need this info to debug" The developer says as their cronjob creates a 250MB csv file, and a few MB of debug logs per day, for the past few years. "Disk is cheap" they say.
As a sysadmin, I hate that too.
- whimsicalism 5y agosometimes the data is just big...
- colechristensen 5y agoOften a considerable portion of those logs are useless, trace level misclassified as info, kept for years for no reason. You should keep a minimal set of logs necessary for audit, logs for errors which are actually errors, and logs for things which happen unexpectedly. What people do keep are logs for everything which happens, almost all of which is never a surprise. One needs to go through logs periodically and purge the logging code for every kind of message which doesn’t spark joy, I mean seem like it would ever be useful to know.
- whimsicalism 5y agosure, in a world where machine learning doesnt exist i would agree with you. for low level logs of things like "memory low, spawning a new container" i would also agree with you. not for user actions though (which is the topic closest to whats under discussion given what sort of data these regulations cover)