# Multiple production logs

**URL:** <https://www.ruby-forum.com/t/multiple-production-logs/83398>\
**Category:** Deployment\
**Created:** [January 25, 2007, 7:29pm UTC](https://www.ruby-forum.com/t/multiple-production-logs/83398 "2007-01-25T19:29:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![asoto](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/58956e/32.png) [@asoto](https://www.ruby-forum.com/u/asoto)\
**Post date:** [January 25, 2007, 7:29pm UTC](https://www.ruby-forum.com/t/multiple-production-logs/83398/1 "2007-01-25T19:29:36Z")

</div>

> So, if each machine’s log is written to a different file, doesn’t it  
> make it difficult to look through each production.log file when you’re  
> trying to track down problems? I wonder if there’s a good way to  
> combine all the log files when you’re debugging.

I’d install splunk ([www.splunk.com](http://www.splunk.com)) and let it co-relate the events  
across logs for you. The free version allows up to 500MB of log data  
to be indexed per day.

---

<div class="post-metadata">

**Author:** ![asoto](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/58956e/32.png) [@asoto](https://www.ruby-forum.com/u/asoto)\
**Post date:** [January 25, 2007, 10:59pm UTC](https://www.ruby-forum.com/t/multiple-production-logs/83398/2 "2007-01-25T22:59:24Z")

</div>

AWStats provides a utility (in the tools directory) called  
logresolvemerge.pl

It stitches together multiple log files into time order.