On 28 Jul 2016, at 23:46, James Perkins <jperkins(a)redhat.com>
I haven't put much thought into a solution for this, but I want to put it out there
to start a discussion.
There is a new feature request  to provide access logs for EJB's. We currently
have at least 3 different places to configure different types of logging.
The logging subsystem
Management access logging
Web access logging
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
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).
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.
+1 for providing access to other log files.
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.
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.
Anyway I'm just looking to plant a seed at this point and see what others think.
James R. Perkins
JBoss by Red Hat
wildfly-dev mailing list