Right, I've dealt with configuring various things from databases in the past, and there is no one-size-fits-all way of doing this. This is why I mentioned a KISS set up if we were to provide anything in that dept.
Gary On Thu, Mar 29, 2018 at 11:39 AM, Ralph Goers <[email protected]> wrote: > I could think of all kinds of weird ways to do this. I could imagine an > Appender table, a Logger table, a Properties table, etc. But at some point > this stuff becomes somewhat free form so the schema would have to account > for that. > > Ralph > > On Mar 29, 2018, at 10:33 AM, Gary Gregory <[email protected]> wrote: > > Interesting. The simplest would be a new JDBC configuration class in Log4j > that gets a complete XML document string from DB table's column... > > Gary > > On Thu, Mar 29, 2018, 11:28 Enric Jaen <[email protected]> wrote: > >> Yes, log4j internally would generate the new xml configuration >> >> >> En jueves, 29 de marzo de 2018 17:05:26 GMT+1, Ralph Goers < >> [email protected]> escribió: >> >> Will a database configuration could certainly be supported somehow, any >> changes to it would most likely still end up in a full reconfiguration as >> that is how Log4j generally handles changes to the configuration it detects. >> >> Ralph >> >> > On Mar 29, 2018, at 8:29 AM, Enric Jaen <[email protected]> >> wrote: >> > >> > Hello, >> > I know is possible to change the configuration file dynamically, but I >> wonder if could be possible to configure appenders from a database, without >> needing to reload the full configuration file. A useful case would be to >> change the log level of the appender. >> > RegardsEnric >> > >> > >> > >> > >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > >
