I've a use case where I am adapting Logback to work with a legacy product's proprietary log mechanism. I did this by creating a wrapper class around a Logger. But there is no hook to programmatically touch the Logger instances at creation-time.

I submitted a pull request #635 (https://github.com/qos-ch/logback/pull/635) that addresses this by simply adding a method to LoggerContext that is invoked immediately after Logger.createChildByName(), which by default is a no-op but can be implemented by custom contexts.