Created a JIRA issue (https://issues.apache.org/jira/browse/LOG4J2-2526). I
have put in the basic information. Please feel free to update it as needed.
Thanks,Bhavesh.
On Friday, December 21, 2018, 8:36:01 AM PST, Ralph Goers
<ralph.go...@dslextreme.com> wrote:
If you haven’t created a Jira issue for this please do. I need to make
modifications to the current file watching logic as I need to be able to
monitor configurations external to the application, such as in Spring cloud or
possibly even in a git repo. It may be that we will want to add a list of paths
or urls to monitor in the configuration.
Ralph
> On Dec 21, 2018, at 8:49 AM, Matt Sicker <boa...@gmail.com> wrote:
>
> I'm also interested in this idea. My current workaround that I'm using for
> refreshing system properties (for example) is to call
> LoggerContext.getContext(false).reconfigure() after updating lookup values.
> I'd imagine we'd need a new API to support the configuration being notified
> of lookup value changes to avoid this, though.
>
> On Thu, 20 Dec 2018 at 16:18, Bhavesh Patel <bhaveshhpa...@yahoo.com.invalid>
> wrote:
>
>> Hi, I have a question about monitor interval on log4j2 configuration
>> file. I know that the monitor interval will work if anything is directly
>> updated in the configuration file. Is there a way to track updates made to
>> any lookups referred in the configuration file using monitor interval?
>> Our issue if that we are using a Kafka Appender and have removed the Kafka
>> bootstrap servers and topic names in a separate abc.properties file. From
>> log4j2.xml, we do a bundle lookup to abc and get the value for Kafka
>> bootstrap server and topic names. We have monitor interval set on
>> log4j2.xml but since Kafka bootstrap server and topic names are not in this
>> file, any updated made to them in the abc.properties file will not be
>> picked up by monitor interval unless the application is restarted.
>> Anyone faced this issue or can suggest any solution for this?
>> Thanks,Bhavesh.
>
>
>
> --
> Matt Sicker <boa...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
