If you have a lot of money splunk is by far the best product on the market: http://www.splunk.com/ Otherwise, besides loggly which I'm not familiar with, you might want to look at http://logstash.net/ (free and open source). I think one of the issues with logstash is that the data storage isn't optimal but it might be fine in your case since you probably don't need to store that much data.
- Matt On Wed, Jul 18, 2012 at 12:30 PM, Ben Wanicur <[email protected]> wrote: > In term of analysis, etc..., I think Loggly is a great solution. I worked > at a large dot com, and we were very happy with this product: > > http://www.loggly.com/ > > I also have a friend (very bright programmer) from that dot com who now > works there. I have not neen exposed to Loggly in several years, but I > imagine it is still a great logging solution. > > Ben > > > > On Wed, Jul 18, 2012 at 8:04 AM, bradleyland <[email protected]>wrote: > >> In our organization, I'm the guy responsible for infrastructure. Most >> aspects of deployment, I've managed to get my hands around, but logging >> still troubles me. Our app is a tool-app that we sell to large businesses >> and municipalities as part of a consulting-heavy product, so our traffic >> levels aren't crazy high 99% of the time. We do, however, have a real-time >> component to our application, which uses polling, so during large events, >> application traffic levels can get up in to areas where I run in to issues >> with request interleaving in the Rails log files. >> >> Rails logging is currently configured with the defaults, so we're using >> the standard BufferedLogger. I really like the multi-line format of the >> standard Rails log, and we've stuffed some additional debugging information >> in to the log, so I'm reluctant to abandon the information we gather. I >> also make use of tools like request-log-analyzer, so that just adds to the >> pain of abandoning file based logging. >> >> I'm wondering what everyone else does for logging in production? I've >> read a few articles on software like Graylog2, but the dependencies really >> turn me off. I'm also considering sticking to something simple, like >> syslog, but syslog & multiline don't go together well. What to do!? >> >> -- >> 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
