[jboss-jira] [JBoss JIRA] (LOGMGR-205) Add ability to watch a logging configuration file for changes and reconfigure the log manager based on the new configuation
Brian Stansberry (Jira)
issues at jboss.org
Mon Oct 8 12:11:00 EDT 2018
[ https://issues.jboss.org/browse/LOGMGR-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644718#comment-13644718 ]
Brian Stansberry commented on LOGMGR-205:
-----------------------------------------
This might be very useful in the cloud.
A container is "immutable", except when it isn't. ;-) And AFAICT the biggest use case for "mutable" is tweaking logging. Currently to do that with an WF/EAP based container the user needs to open a terminal in the container and then run the CLI. Which is very WF/EAP specific.
Any kind of more general purpose solution would require some kind of "logging configuration API." And for Java, some logging.properties dialect variant (presumably jul) is a _possible _part of that. The other part possibly being use of ConfigMap. So, users configure logging via a logging.properties in the correct dialect in a ConfigMap. And if they update the config map the container detects and reacts. Or probably the default config is in standalone.xml with the ConfigMap only being a way to override the default or push changes.
There are a lot of issues with this idea, e.g. the scope of the config map content both across pods and across time (ConfigMap is not versioned), so what I describe above is nothing more than vague handwaving thought. But anyway, this RFE opens up some possibilities.
[~rcernich] FYI.
> Add ability to watch a logging configuration file for changes and reconfigure the log manager based on the new configuation
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: LOGMGR-205
> URL: https://issues.jboss.org/browse/LOGMGR-205
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
>
> It could be useful to add a utility to watch a {{logging.properties}} file for changes and reconfigure the log manager based on these changes.
> As a test I've created an [example|https://gist.github.com/jamezp/68cd45982ba2b75aa2e95465695ec061] which could use some better options for removing no longer used configured objects.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list