> Logging has always been one of the least customizable and rudimentary > parts of Rails. It is true that you can swap out different logging > solutions, but it practice it either requires monkey patching > BufferedLogger or reimplementing all of its methods.
I was under the possibly mistaken impression that with the exception of our log initialization code, we only relied on the public API for the Logger class from ruby's stdlib. I've used both Logger.new and sys log logger without any issues, what did you have to monkeypatch? That definitely sounds lame. > I would advocate > that Rails should use something like the lumberjack gem (http:// > github.com/bdurand/lumberjack) in place of BufferedLogger. This sort > of architecture would provide Rails with a standard, supported logging > interface, and allow for better log formats and a simpler means of > writing messages to non-file based devices (syslog, mongodb, etc.). All of this stuff should be possible by simply providing an alternative implementation of Logger, no? -- Cheers Koz -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
