4 ms·
The difference between deploying once and deploying just to add more logs. And more logs is a huge difference. I don't know about your environment but I can't p
by invalidname 4y ago
The difference between deploying once and deploying just to add more logs. And more logs is a huge difference. I don't know about your environment but I can't push something to production on my own schedule. I need approval, process, etc.
This is painful to do just to add a log which might not include all the information I need.
- geophile 4y agoThe more constraints you have on pushing something to production, the less it makes sense to deploy logging dynamically! Those constraints are there to minimize risk, ensure quality and security, etc. Dynamically deployed logging seems to provide an extremely large loophole. For example, consider the recent Java logging fiasco.
- invalidname 4y agoExcellent point. The tool we use (Lightun) runs all of that in a read-only sandbox and limits the classes you can access (they are in a sandbox too) so you can't print "anything". It throttles your access so you won't use too much CPU with expensive operations too. It also comes with PII reduction and block lists so you won't just log user passwords in the login code... This solves the problem of over-logging: https://www.reddit.com/r/devops/comments/udgohy/there_is_no_such_thing_as_too_much_logging_or_is/ https://www.reddit.com/r/devops/comments/udgohy/there_is_no_...