[
https://issues.jboss.org/browse/WFLY-6892?page=com.atlassian.jira.plugin....
]
James Perkins commented on WFLY-6892:
-------------------------------------
Just adding my same comment here as this would likely be looked at first when the work
starts.
{quote}
One thing we should start to consider is where/how these will be configured. Currently
management access logs are configured under {{/core-service=management/access=audit}} and
web access logging is configured under
{{/subsystem=undertow/server=default-server/host=default-host/setting=access-log}}. The
resources also have different models, log to different locations, etc. We should consider
whether there should be a central place these can be configured or not.
{quote}
To follow up on that too there is currently a log viewer that can view the plain text
versions of only the logs defined on the logging subsystem. There has been some discussion
around providing a better log viewer which can filter data resulting in requiring some
kind of structured data. I assume there will be users wanting to view all these logs
through the log viewer. Especially in a containerized environment. It really does seem we
need to move to some kind of global solution.
Access logging for EJBs
-----------------------
Key: WFLY-6892
URL:
https://issues.jboss.org/browse/WFLY-6892
Project: WildFly
Issue Type: Feature Request
Components: EJB
Affects Versions: 10.0.0.Final
Reporter: Brad Maxwell
Access logging for EJB requests similar to Web access logging would be very useful.
Possibly something like:
{code}
[date-time] [host/IP of caller] [EJB Name] [EJB Method] [invocation id] Request Received
...
[date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Starting
Invocation ...
[date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Finished
Invocation ...
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)