You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Dave Ariens (JIRA)" <ji...@apache.org> on 2015/03/19 19:23:42 UTC
[jira] [Updated] (LOG4J2-979) Configuration Reload Callback
[ https://issues.apache.org/jira/browse/LOG4J2-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Ariens updated LOG4J2-979:
-------------------------------
Description:
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 of 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.
was:
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 of monitorInterval="30".
https://dropwizard.github.io/metrics/3.1.0/manual/log4j/
When troubleshooting we modify the root the 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.
> 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 of 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org