[jboss-jira] [JBoss JIRA] (WFLY-4519) Customizable Console Log Viewer

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060704#comment-13060704 ] 

James Perkins commented on WFLY-4519:
-------------------------------------

This was intentionally limited to the {{jboss.server.log.dir}}. The main reason being we didn't want the log viewer to become a file server. It could also be a potential security hole.

A workaround would be to use the {{jboss.server.log.dir}}, but during boot add {{-Djava.server.log.dir=/apps/logs}}. That would, by default, put logs into the {{/app/logs/server-name}} directory. 

> Customizable Console Log Viewer
> -------------------------------
>
>                 Key: WFLY-4519
>                 URL: https://issues.jboss.org/browse/WFLY-4519
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Logging
>    Affects Versions: 9.0.0.Beta2
>            Reporter: Carlton Zachary
>            Assignee: James Perkins
>
> Currently the Console log viewer only points to jboss.server.log.dir.  In our Domain environment we have our server.log write to a non-default location.  This is defined in the host-slave.xml as:
> <paths>
>          <path name="custom.jboss.server.log.dir" path="/apps/logs/server1"/>
> </paths>
> it is then referenced in the domain.xml file logging subsystem as:
> <file relative-to="custom.jboss.server.log.dir" path="server.log"/>
> Can the Console logviewer be enhanced to allow it to be configured to point to a custom server.log location?
> https://bugzilla.redhat.com/show_bug.cgi?id=1191180
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)