bumi / request-log-analyzer forked from wvanbergen/request-log-analyzer
- Source
- Commits
- Network (23)
- Downloads (29)
- Wiki (1)
- Graphs
-
Branch:
master
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Fri Jun 12 04:09:02 -0700 2009 | |
| |
DESIGN.rdoc | Wed Jun 24 10:52:06 -0700 2009 | |
| |
LICENSE | Thu Aug 14 11:16:37 -0700 2008 | |
| |
README.rdoc | Mon Jul 13 14:59:27 -0700 2009 | |
| |
RELEASE_NOTES.rdoc | Wed Jul 15 08:53:15 -0700 2009 | |
| |
Rakefile | Fri Jun 12 04:09:02 -0700 2009 | |
| |
bin/ | Tue Sep 01 22:17:57 -0700 2009 | |
| |
lib/ | ||
| |
request-log-analyzer.gemspec | Wed Jul 15 08:56:03 -0700 2009 | |
| |
spec/ | Mon Jun 22 13:40:57 -0700 2009 | |
| |
tasks/ | Mon Jun 22 13:11:24 -0700 2009 |
Request-log-analyzer
This is a simple command line tool to analyze request log files of both Rails and Merb to produce a performance report. Its purpose is to find what actions are best candidates for optimization.
- Analyzes Rails log files (all versions), Merb logs, or any other log format you specify
- Combines multiple files and decompresses compressed files (handy if you are using logrotate)
- Uses several metrics, including cumulative request time, average request time, process blockers, database and rendering time, HTTP methods and statuses, Rails action cache statistics, etc.) (Sample output: wiki.github.com/wvanbergen/request-log-analyzer/sample-output)
- Low memory footprint and reasonably fast (server-safe)
- MIT licensed
Request log analyzer was designed and built by Willem van Bergen and Bart ten Brinke.
Installation
Install request-log-analyzer as a Ruby gem:
$ sudo gem install request-log-analyzer
Alternatively, use the gem from the GitHub gem server:
$ sudo gem install wvanbergen-request-log-analyzer --source http://gems.github.com
To get the best results out of request-log-analyzer, make sure to set up logging correctly: wiki.github.com/wvanbergen/request-log-analyzer/configure-logging for your application.
Usage
To analyze a log file and produce a performance report, run request-log-analyzer like this:
$ request-log-analyzer log/production.log
For more details and available command line options, see the project’s wiki: wiki.github.com/wvanbergen/request-log-analyzer/basic-usage
Additional information
Do you have a rails application that is not performing as it should? If you need an expert to analyze your application, feel free to contact either Willem van Bergen (willem@railsdoctors.com) or Bart ten Brinke (bart@railsdoctors.com).
- Project wiki at GitHub: wiki.github.com/wvanbergen/request-log-analyzer
- railsdoctors homepage: railsdoctors.com
- wvanbergen’s blog posts: techblog.floorplanner.com/tag/request-log-analyzer
- barttenbrinke’s blog posts: movesonrails.com/articles/tag/analyzer

