not sure of the degree of your additional debug info, but the last 10 minutes of this talk from RailsConf Austin covers how they do logging in the new basecamp and may add to your forensic logging strategy.
http://www.youtube.com/watch?v=oXTzFCXE66M&feature=player_detailpage#t=2473s best, steven On Wed, Jul 18, 2012 at 9:11 PM, Matt Aimonetti <[email protected]>wrote: > Logstach is self hosted can read log files and support multilines log > events. > > -m > Sent from my iPad > > On Jul 18, 2012, at 8:21 PM, bradleyland <[email protected]> wrote: > > Thanks for all the great suggestions, everyone. Like Adam, sending log > data to a third-party is problematic for us. That pretty much rules out > service-based solutions. I was hoping to find a solution like syslog, but > that handles multiline log entries a little more gracefully. > > I talked to another friend who works at a Rails shop out of Toronto, and > he said they're still using file-based logging and simply prepending each > log entry with the PID of the process writing to the log. I think I'm > probably going to go that route, then write a simple toolchain that can > reconstruct log files and serialize entries for specific date ranges. Like > most, we only need logs when something goes wrong, so it's almost always a > forensic endeavor. > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
