As I have already said many times, I fully support this initiative. Tomcat has done this move a while ago and it was a great success.
Cyrille On Wednesday, April 4, 2018 at 3:18:00 PM UTC+2, Baptiste Mathus wrote: > > Hello everyone, > > Having worked on more things related to Jenkins logging recently, I've had > the opportunity to remember my past pain when I was operating a Jenkins > instance and sending logs to an ELK cluster. > Compared to almost everything else in the infrastructure, the logstash > rules for Jenkins logs were unnecessarily complex. > > The main pain-points, for me at least, had been the two-lines (sigh) per > log default, and also the localized date format (or log level...). > Even now, so many years after reading those, I still struggle daily to > make sure I'm reading the right line/date associated to the message I'm > reading on the line above. > > I would like to propose we change the current logging format behavior to a > more readable and more operation-friendly one. > This would result in something close to the following format: > > [ INFO][2018-04-04 12:40:49] Logging initialized @180ms to > org.eclipse.jetty.util.log.JavaUtilLog (from org.eclipse.jetty.util.log.Log > initialized) > [ INFO][2018-04-04 12:40:49] Beginning extraction from war file (from > winstone.Logger logInternal) > [WARNING][2018-04-04 12:40:49] Empty contextPath (from > org.eclipse.jetty.server.handler.ContextHandler setContextPath) > [ INFO][2018-04-04 12:40:49] jetty-9.4.z-SNAPSHOT (from > org.eclipse.jetty.server.Server doStart) > > Instead of the usual: > > Apr 04, 2018 12:36:41 PM org.eclipse.jetty.util.log.Log initialized > INFO: Logging initialized @354ms to org.eclipse.jetty.util.log.JavaUtilLog > Apr 04, 2018 12:36:41 PM winstone.Logger logInternal > INFO: Beginning extraction from war file > Apr 04, 2018 12:36:42 PM org.eclipse.jetty.server.handler.ContextHandler > setContextPath > WARNING: Empty contextPath > Apr 04, 2018 12:36:42 PM org.eclipse.jetty.server.Server doStart > INFO: jetty-9.4.z-SNAPSHOT > > > WDYT? > > If this looks interesting to people, I'm ready to file the associated JEP > for it and possibly work on its implementation in the future. > > Obviously, we would need some way to revert to the "legacy" format, at > least for some time for users to adapt. But that is not something I'm > particularly worried about. > > -- Baptiste > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3593c7a5-6f77-4dc7-94f8-e2d8cad4b521%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
