<div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">FWIW there are 3 options:</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">1) Default on.</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">2) Default off, not specified in standard configs.</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">3) Default off, but set to on in standard configs.</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">The distinction between 1 and 3 is people bringing an existing config do not see a behavior change.</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">No matter which we do we should aim to get this in very early in a release dev cycle so we have time to notice any odd impacts.</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Do you have any thoughts on how we can look for odd impacts? IIRC the odd impact would be stuff we expect to appear in the server.log no longer appearing there.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 10, 2020 at 5:50 PM James Perkins <<a href="mailto:jperkins@redhat.com">jperkins@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello All,<div>I've got an open proposal for some changes with how log messages may be routed [1]. There is some discussion on there with some concerns about messages that the user may not expect to be routed to their own specific log context. Feedback from a wider audience would be appreciated.</div><div><br></div><div>Currently I've got this enabled by default which would be a change in behavior. However, as I've stated in a comment on the proposal, maybe it's better to opt-in than opt-out. Either way any feedback would be appreciated.</div><div><br></div><div>Thanks in advance.<br><div><br></div><div>[1]: <a href="https://github.com/wildfly/wildfly-proposals/pull/281" target="_blank">https://github.com/wildfly/wildfly-proposals/pull/281</a></div><div><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>James R. Perkins</div><div>JBoss by Red Hat</div></div></div></div></div></div></div></div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Brian Stansberry<div>Manager, Senior Principal Software Engineer</div><div>Red Hat</div></div></div>