Thanks ... interesting. This certainly looks interesting ... will have to give it a whirl.
The really nice thing about using the syslog mechanism is that all your permissions and log file ownership is easy (any system user can write to the log) whereas if you are just >> to a file then you sometimes have to run all the batch processes as www-data (apache) which sometimes makes me a touch uncomfortable. And the remote logging stuff is quite handy in some cases. cheers. == Andrew Boag Director +61 421 528 125 [email protected] On 05/05/2011, at 10:49 am, Nicholas Faiz wrote: > 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. -- 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.
