Hi Andrew, I have done this before, but it was in 2008 (I think) and was part of steps to monitor some performance problems in an app. Anyway, I used http://rails-analyzer.rubyforge.org/tools/classes/SyslogLogger.html .
To me this doesn't feel like the way to approach the problem, though, or perhaps I'll have to read up on what I can do with syslogs a bit more (which I will do now - thanks). Cheers, Nicholas -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
