[ https://issues.jboss.org/browse/WFLY-7880?page=com.atlassian.jira.plugin.... ] Davy Steegen updated WFLY-7880: ------------------------------- Description: When using "per deployment logging", the WildFly 10 admin console does not show the log files that I configured in my log4j configuration (only those that are managed via the WildFly itself). You can find an example log4j configuration in the attachments. It contains a File appender that logs in a file called client.log (relative to the WildFly log directory). The workaround is to create a Logging Handler of type File in the admin console per log file I want to monitor in the admin console. However, in our case the WildFly is managed by another team. We don't want to botter them each time we add a new log file. Am I missing something or does this work as designed ? was: When using "per deployment logging", the WildFly 10 admin console does not show the log files that I configured in my log4j configuration (only those that are managed via the WildFly itself). You can find an example log4j configuration in the attachments. It contains a File appender that logs in a file called client.log (relative to the WildFly log directory). The workaround is to create Logging Handler of type File in the admin console per log file I want to monitor in the admin console. However, in our case the WildFly is managed by another team. We don't want to botter them each time we add a new log file. Am I missing something or does this work as designed ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)