Edwin F. López created LOG4J2-913:
-------------------------------------
Summary: Allow to load log4j2 configuration from a centralized
repository, like a database or a webservice
Key: LOG4J2-913
URL: https://issues.apache.org/jira/browse/LOG4J2-913
Project: Log4j 2
Issue Type: New Feature
Components: Configurators
Environment: All
Reporter: Edwin F. López
Priority: Critical
Hi.
I've worked in some projects that require having a single configuration point
for all my loggers since basically, all of them are web applications. Since
controlling the logging event flood can be problematic when the applications
are in production, it would be great if, along with the current
XMLConfiguration and JSONConfiguration, there would be a configuration
mechanism that could load the log4j2 from a remote location, whether it's a
webservice (SOAP, ReST) or a database.
The contract can be summarized like this:
* Set a configuration endpoint
* Set a polling interval
* Allow authentication
* Load a given named configuration
* Reconfigure if required.
Right now, I'm been scratching this need by code, using a
ScheduledExecutorService and a pice of code like this:
{code:java}
LoggerContext ctx = null;
URI uri = null;
try {
uri = new
URI("http://localhost:7001/log4j2config/getlog4j2xmlconfig?appCode=log4jConfig§ion=full";);
} catch (URISyntaxException e) {
System.err.println(e.getMessage());
}
ctx = Configurator.initialize("Log4J2Conf",
Thread.currentThread().getContextClassLoader(), uri);
ctx.start();
{code}
However, I believe that since this is a common scenario, it could be
implemented as a new plugin.
Thank you very much.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
