> Now compare the efficiency of minimal logging compared to lotsa logging (even if most of it is only conditionally enabled), when optimising for dev time spent on troubleshooting :)
Or even for successful requests per second averaged over spans of time including normal outages, degradations, and other indignities of life. It doesn't take many minutes at zero throughput to drag those averages down, so every minute shaved off by more illuminating logging is a performance benefit.
Re:Logging Performance Comparison
by frant-hartm on Monday July 11, 2022 @03:16AM
(#32053217)
Both Log4j2 and Logback support automatic reloading of the configuration file at a regular interval - just update the file and the log library picks it up after X seconds.
Should work well with K8s config map mounted as volume.
The one thing from modern Java logging I love and miss in other languages is being able to set log levels on specific loggers while the app is running.
Yeah it involves JMX, which has an annoying protocol that insists on domain names that you can resolve, making it a PITA with K8s from your local terminal, but it's such a QoL feature.