[
https://issues.jboss.org/browse/LOGMGR-205?page=com.atlassian.jira.plugin...
]
James Perkins commented on LOGMGR-205:
--------------------------------------
We could just use the {{logging.properties}} to configure logging for the cloud. However
we'd lose some things like per-deployment logging and logging profiles.
The ConfigMap sounds interesting though. I don't know much about that, but OT for this
it would be interesting if possible to have a ConfigMap to CLI type of thing. However that
doesn't really make the configuration immutable.
More of a WildFly thing, but one thing I've thought of too is not using the XML config
file for the logging configuration. Essentially the model would be based on a
{{logging.properties}} rather than the XML. There are some issues with system properties,
paths, etc. that make this not quite work right however. The ability to listen to a file
for changes would allow either a management interface or editing the raw file to work
though. Though like I said working around the paths ({{relative-to}}) and system
properties is a problem.
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)