[
https://issues.jboss.org/browse/WFCORE-1549?page=com.atlassian.jira.plugi...
]
James Perkins moved WFLY-6601 to WFCORE-1549:
---------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-1549 (was: WFLY-6601)
Component/s: Logging
(was: Logging)
Affects Version/s: (was: 10.0.0.Final)
Application context specific log handler
----------------------------------------
Key: WFCORE-1549
URL:
https://issues.jboss.org/browse/WFCORE-1549
Project: WildFly Core
Issue Type: Feature Request
Components: Logging
Reporter: Nicklas Karlsson
Assignee: James Perkins
There are many cases where it would be handy to group log events on some application
specific information (e.g. placed in the MDC). Examples are
* Collecting all user session interaction loggings into a separate file
* Collecting all log entries related to a specific client machine into a separate file
* Collecting the entire lifecycle of an entity (long-lived order, process etc) into a
separate file
This could perhaps be implemented with a LogFilePolicyClass that would return the correct
(existing or fresh) file based on the MDC data?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)