2018-04-04 18:12 GMT+02:00 Oleg Nenashev <o.v.nenas...@gmail.com>:

> Hi Baptiste,
>
> Anyone can easily change the logging format in Jenkins by passing custom
> J.U.L properties file.
>

Yes. But in practice, I'm convinced virtually nobody does this.


> 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.
>

FTR, I did consider this strategy about keeping the current behavior, and
introduce some sysprop to enable the new (and much much better, IMO)
behavior.
But this is IMO not the way we provide the best possible Jenkins experience
to users, especially newcomers.

And I don't think we should consider Jenkins Essentials to be the only
place where we make the OOTB experience as smooth as possible.

Do you really see a big issue if we offer a sysprop to revert to the
current behavior, *but* change the default to something more sensible?
I fail to see how hard it would be for people having built monitoring about
Jenkins logs to just temporarily use the sysprop while they adapt their
logstash or whatever parsing rules.
I can even probably provide it for logstash at least.

And again, this is IMO for the good of the project and its users, so even
if there's some (small) disruption this is probably worth it.

Thanks a bunch for your feedback in any case.

-- 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS48-5JTQKOSjt9dtFRimET-%3DH9JKGNh0OoWnKwq6QS0Gg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to