<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 28 Jul 2016, at 23:46, James Perkins <<a href="mailto:jperkins@redhat.com" class="">jperkins@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I haven't put much thought into a solution for this, but I want to put it out there to start a discussion.<div class=""><br class=""></div><div class="">There is a new feature request [1] to provide access logs for EJB's. We currently have at least 3 different places to configure different types of logging. </div><div class=""><ol class=""><li class="">The logging subsystem</li><li class="">Management access logging</li><li class="">Web access logging</li></ol><div class="">All 3 of these reside under different resources and have different configuration options. Which is really understandable since they are all quite different in what they are trying to do.</div></div><div class=""><br class=""></div><div class="">However since we may be adding a forth now I'm thinking we should start to consider some other options for these. Possibly some kind of centralized location to configure logging in or something that all log messages pass through to ensure they're routed correctly (yes I realize this is essentially a log manager).</div><div class=""><br class=""></div><div class="">As it is now we do have the ability to download logs from a server. Audit logs, web access logs, process controller logs and host controller logs can not be downloaded or viewed from the log viewer on the web console. I again assume user would like access to all log files or some way to view all log messages.</div></div></div></blockquote><div><br class=""></div><div>+1 for providing access to other log files. </div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">I'm mainly bringing this up because I'm guessing for things like WildFly Swarm and OpenShift log files aren't all that useful as the user has no access to them. Pushing log messages to some kind of log aggregation server in these cases is often useful in these situations.</div><div class=""><br class=""></div><div class="">At a minimum I do think we need to provide a way to download or view all log files. In managed domains this is probably useful as well as environments like docker.</div><div class=""><br class=""></div><div class="">Anyway I'm just looking to plant a seed at this point and see what others think. </div><div class=""><br class=""></div><div class="">[1]: <a href="https://issues.jboss.org/browse/WFLY-6892" class="">https://issues.jboss.org/browse/WFLY-6892</a><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class="">James R. Perkins</div><div class="">JBoss by Red Hat</div></div></div></div></div>
</div></div>
_______________________________________________<br class="">wildfly-dev mailing list<br class=""><a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/wildfly-dev</div></blockquote></div><br class=""></body></html>