RailsLogVisualizer: now open source and 6 x faster.
I moved the RailsLogAnalyzer to RubyForge and as there was already a project on RubyForge with the same name, so I renamed it to RailsLogVisualizer. So RailsLogVisualizer it is. Version 0.3 provide a drastic speed improvement over version 0.2. If you are curious or adventurous you can browse the source code on RubyForge.
The Project Home Page is http://railslogvislzr.rubyforge.org/
The project is at http://rubyforge.org/projects/railslogvislzr/
Enjoy!
The Project Home Page is http://railslogvislzr.rubyforge.org/
The project is at http://rubyforge.org/projects/railslogvislzr/
Enjoy!
RailsLogAnalyzer v0.2 for OSX - Faster, Better
Version 0.2 of the RailsLogAnalyzer is still a development version but a great improvement over my first prototype. This version has been rewritten from the ground up and doesn't use a database to store intermediate log file aggreation.
Analyzing your log file data.
Once the log file is loaded you will see a breakdown of your requests by year, month, and day.
Click on the year, month, or day to see the controllers invocations during that period.
Click on the controller in the chart to see the method invocations during the selected period.
The method are further broken down based on their http methods (get, post, delete, ...).
Note: loading a 10Mb production log file with 30000 requests takes about 10 seconds on my MacBook Pro.
loading a 250Mb production log file with 530000 requests takes about 2 minutes.
loading a 4.5Gb production log file with 11 million request takes about 45 minutes.
The data is loaded in memory and must be reloaded once the application is closed.
Download it here RailsLogAnalyzer_0.2.dmg (487KB) and let me know your findings at daniel@onrails.org
Analyzing your log file data.
Once the log file is loaded you will see a breakdown of your requests by year, month, and day.
Click on the year, month, or day to see the controllers invocations during that period.
Click on the controller in the chart to see the method invocations during the selected period.
The method are further broken down based on their http methods (get, post, delete, ...).
Note: loading a 10Mb production log file with 30000 requests takes about 10 seconds on my MacBook Pro.
loading a 250Mb production log file with 530000 requests takes about 2 minutes.
loading a 4.5Gb production log file with 11 million request takes about 45 minutes.
The data is loaded in memory and must be reloaded once the application is closed.
Download it here RailsLogAnalyzer_0.2.dmg (487KB) and let me know your findings at daniel@onrails.org
RailsLogAnalyzer – help wanted
I need some Mac users to test and give feed back on a very early version of the RailsLogAnalyzer. This app is an OSX app and not deployed on a server, so I would like to find out the obvious bug that may occur on different Macs. I tried it on my own MacBook Pro, G5 server, and on an old PowerBook G4. But then again the people most likely to use it are Rails developers that may have differences in their environment.
So if you like to take risks :-), understand the basic structure of a Rails app, have a production.log you want to analyze, and are not afraid of some scary bugs then read on…
