I\'ve built a solution based on the answer in my previous question Redirect logger output for a specific controller in Rails 3 for Rails 3. It works great however now I am tryin
The approach of using a different logging class for 1 controller has the downside that it won't work on a threading server which is in fashion these days not just with JRuby, but MRI too thanks to Heroku
Only idea I have so far after giving it a week of thought is to pipe the logs to syslog and use syslog's facilities to split them into separate files.
It would still require patching the Logger
to include strings that would allow for the splitting (such as adding a formatted lined of from the #caller
trace to the log files).
Plan B would be to introduce my own logger and simply log what I need in that controller. You could easily dump params and response for example if that's enough