How to tell loggers to inherit filters from the parent?

[sflanigan]

This relates to the old discussion Re: JBoss 7 log configuration not working as expected  and [LOGMGR-45] Have loggers inherit filters - JBoss Issue Tracker

I have a similar problem because I need to see the stack trace whenever Weld catches an exception, which it then logs as DEBUG with one of 21 different loggers. Ideally I would use configuration almost like this on the top-level log category:

/subsystem=logging/logger=org.jboss.weld:add

/subsystem=logging/logger=org.jboss.weld:write-attribute(name=level,value=DEBUG)

/subsystem=logging/logger=org.jboss.weld:write-attribute(name=filter-spec, value="any(match(\"Catching\"), levelRange[INFO, FATAL])")

I gather jamezp added the ability to inherit filters from parent loggers back in 2015 (Logger now has a method setUseParentFilters),  but I can't work out how to use it. How can I set the logger attribute useParentFilters from JBoss CLI (or standalone*.xml) so that the filter can be inherited by child loggers? And would I set it on the parent logger, or would I have to set it on each of the child filters?

[jamezp]

Hi Sean,

I never did add the functionality to WildFly for some reason. I've filed [WFCORE-3462] Expose the ability for filters on loggers to be inherited - JBoss Issue Tracker to track the issue however.

Currently the best way to use filters would be on a handler. I realize matching on something like "Catching" probably isn't ideal on a handler, but it would currently be the only way without writing a custom handler.

--

James R. Perkins

[sflanigan]

Thanks jamezp.

Turning on DEBUG logging for all of Weld could be pretty expensive, so perhaps I'm better off enumerating the sub-loggers which really need DEBUG to be enabled anyway. It will still be good to specify the filter exactly once, so I'll try putting it on the handler for now, as you suggest.