I added the -c configuration option to the documentation and I have added your suggestions to the TODO file. If you have some spare time to hack on it, please do so!

As for the routes: I assume that if the code was bedded into a plugin/gem, it could then easily access the routes (and it would also know where to find the logfiles). It could then also add a rake or cap task, which would make it easier to aggregate the log analysis from your applications.

Alternatively, I could imagine passing a hash to analyze.rb for custom routes would be an option, which would then be feeded into the request_hasher method (as manually editing analyze.rb is a pain as you’d have to do it each time you publish a new version of analyze.rb).

Currently, the analyzer will use some simple guesses to aggregate URLs. It does not use the Rails routing file. We are working on it to make it more reliable, but unfortunately it is not that easy. We are looking at it!

In the mean time, you can change how URLs are aggregated by changing the request_hasher method in analyze.rb. You could add a line similar to url.gsub!(/\/markets\/\w+/, '/markets/:id')

You can get more than ten results by passing -c 50 to the command line, which will yield the top 50 results for every statistic.

map.market ‘markets/:id’, :controller => ‘markets’, :action => ’show’

will not create an aggregated “/markets/:id/” in the statistics, but instead create one line per id. This might also be caused by using a custom to_param which isn’t integer (I havn’t checked if that’s the real reason for the problem yet).

Besides that it would be great to have an option to show more than the top10.