I think I already claimed my hate for this logging format many times. For sure I understand Oleg's concern with the impact of changing the default settings. Like always for such kind of change when we don't really know how it could impact our users I would prefer to introduce the change non activated by default in 2.x and wait a 3.x for the change of the default value but if we have to wait for 500 weeklies before the 3.x ..... I'm a bit septic about my approach
On Wed, Apr 4, 2018 at 7:45 PM, Carlos Sanchez <[email protected]> wrote: > I'm +1 to change the format. 2 lines is really annoying > > On Wed, Apr 4, 2018 at 7:24 PM, R. Tyler Croy <[email protected]> wrote: > >> (replies inline) >> >> On Wed, 04 Apr 2018, Oleg Nenashev wrote: >> >> > Hi Baptiste, >> > >> > Anyone can easily change the logging format in Jenkins by passing custom >> > J.U.L properties file. >> > So it should not be a problem to change logging format even if you do >> not >> > add a custom logging appender for ELK. >> > >> > Changing a default logging format may cause regressions in existing >> > monitoring systems. I would rather be conservative and keep the default >> > logging format in Jenkins unless there is a strong justification to do >> > that. New subprojects like Jenkins Essentials and Jenkins X could easily >> > change the default format, because they have no compatibility >> commitment so >> > far. >> >> >> Thanks for sharing your thoughts Oleg, it makes me wonder: how could we >> quantify the positive/negative impact of this (arguably) "bad default." >> >> I'm reminded of some of the pre-Jenkins 2 discussions about security >> defaults >> for example. I spent some time trying to discover Jenkins-log-parsing >> projects, >> tools, and their communities to which we could reach out. Unfortunately I >> wasn't able to find anything big past a couple of blog posts :-/ >> >> From my personal experience as an Operator, compact and easily parseable >> (sed/awk/perl) one-line logs are HUGELY valuable and worth any temporary >> heartburn some people may experience with their existing hacks. >> >> >> >> Cheers >> >> - R. Tyler Croy >> >> ------------------------------------------------------ >> Code: <https://github.com/rtyler> >> Chatter: <https://twitter.com/agentdero> >> xmpp: [email protected] >> >> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F >> ------------------------------------------------------ >> >> -- >> 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/ms >> gid/jenkinsci-dev/20180404172432.wlr4c5f35tuvnijj% >> 40blackberry.coupleofllamas.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CALHFn6NsdOsMRtD%3DacAATvOiY_Wo15gxu6Fwh5iRCs3ogqMmfQ% > 40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NsdOsMRtD%3DacAATvOiY_Wo15gxu6Fwh5iRCs3ogqMmfQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- 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/CAFNCU-_ck5Tc0gbvBqDDMqnUnBtvnHP3cRUaapfcvJJ6jCmDyg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
