Break out Wirebox debug logging to separate logger
When setting a Coldbox root logger `levelMax` to root, if you are trying to debug application-specific items, the log output is almost unusable, because of the Injector.cfc instance creation logs can take up so much of the log file and span multiple lines through the file. This can result in thousands of lines of log files as components are autowired and significantly slow down the application.
A suggestion would be to move the injector and framework debug logging to a separate logger, which would allow the application to configure the `levelMax` for just the framework logging
I think “off” will do what I need this to do
I can’t because it contains client specific items and the log level max is downgraded in the environment methods. I can point you to it offline
The wirebox debug is necessary when actually building wirebox. If not, it becomes impossible to detect issues in wirebox due to multiple recursions, injections,etc. Do you have the coldbox package under a certain log level? Do you mind posting your config
I’ll take a look at using the off array, for this case. It’s a tricky question, because I can’t really ever think of a case where I would need to see the massive dumps of Wirebox injection data, but there might be one. Let’s mark this as declined and I can add something to the Logbox docs to clarify how to restrict debug output to the actual application
You can disable classes as well by using the off =  array. You can disable logging of any particular path or class path if you want. I also don’t recommend opening the floodgates because that’s what’s expected. Why not just choose specifically what you want to debug in a class path like: debug = [ “myapp” ] being myapp your mapping. Then only those categories with that path will be in debug mode.