[
https://issues.apache.org/jira/browse/LOG4J2-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371482#comment-14371482
]
Dave Ariens commented on LOG4J2-979:
------------------------------------
Worked like a charm:
https://gist.github.com/ariens/78504d5e23e33b6aaae4
Thanks!
> Configuration Reload Callback
> -----------------------------
>
> Key: LOG4J2-979
> URL: https://issues.apache.org/jira/browse/LOG4J2-979
> Project: Log4j 2
> Issue Type: Wish
> Components: Configurators
> Affects Versions: 2.2
> Reporter: Dave Ariens
> Priority: Minor
>
> I am curently using io.dropwizard.metrics for instrumenting log4j2 which
> allows me to trend WARN and higher logs as they are generated within my
> log4j2 enabled applications configured with monitorInterval="30".
> https://dropwizard.github.io/metrics/3.1.0/manual/log4j/
> When troubleshooting we modify the root log level in our log4j2 xml
> configuration accordingly and look for issues. This however doesn't take
> effect on the downstream trending and log graphs.
> Ideally, I would like to register a callback for when log4j2 reloads it's
> configuration so I can react accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
