This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
Changelog
Master
Nothing new yet!
Request-log-analyzer 1.5 release cycle
Version 1.5.1
- Fixed a crasher bug in the HTML output of traffic reports.
Version 1.5.0
- Added file format autodetection: in most cases, providing the
--formatparameter is no longer needed to select the correct file format. However, it is still possible to explicitly set the format if autodetection fails. - Added a MySQL slow query log parser (
--format mysql).
Thanks Bart Zonneveld for contributing this functionality. - Mail host now configurable. Use
--mailhost <server>to specify this - Added specs to test mailing functionality using a mock SMTP server (mailtrap)
Request-log-analyzer 1.4 release cycle
Version 1.4.2
- Added correct content-type to emails sent via the
--mailoption.
Version 1.4.1
- Fixed
--mailcommand line option which was broken since version 1.4.0. - Added Scout & Munin plugin integration tests
Version 1.4.0
- Initial version of request-log-analyzer API.
- Added standard deviation to duration and traffic reports.
- Added
--report-amount <n>to define the number of entries in the table in the report. Useallto specify that all entries should be included. The default value is 20 - Added
--report-sort <sortings>options to specify how the resulting duration and traffic tables should be sorted. You can specify multiple sort fields using a comma separated list, which results in multiple tables. Supported sortings aresum,mean,stddevandhits. The default value issum,mean. - Restructured the Rails request log parser to be more flexible about what lines to parse, using the
--rails-format <lines>command line switch.--rails-format minimalwill only parse processing and completed lines.--rails-format productionwill parse exceptions and cache hits besides the minimal lines.--rails-format developmentwill also parse SQL queries and template renderings--rails-format allwill parse every known line type.--rails-format minimal,failurewill parse the minimal lines and exceptions. Use a comma-separated list like this. to define your own line set.
- Significantly improved the test coverage of the Rails log format.
Request-log-analyzer 1.3 release cycle
Version 1.3.7
- Fixed a crasher bug when parsing compressed files.
- Speed optimizations by enabling teaser checks for lines.
Version 1.3.6
- Speed optimizations to improve parsing performance of frequently called methods, i.e.
Tracker#should_update,Request#convert_value,Request#convert_timestamp,Request#convert_trafficandRequest#convert_duration. - Tweaked all file formats for increased performance
- Cleaned up and simplified some old code.
Version 1.3.5
- Added statistics about data traffic for the file formats that contain this information (Apache, Amazon S3, Rack)
- Added support for Rack CommonLogger logs (
--format rack). - Added “agent” and “referer” Apache log format constants.
- Improved request duration parsing (%D directive) from Apache access log files.
- Fixed a bug in the database inserter that caused tables to be created with wrong fields.
Version 1.3.4
- Added Amazon S3 access log parser. Add
--format amazon_s3to you command line to use it. S3 access logs are disabled by default. See the S3 documentation on server logging for more information to enable it.
Version 1.3.3
Retracted release
Version 1.3.2
- Tweaking to increase performance significantly.
- Added a
--no-progresscommand line switch to disable the progress bar parsing for an additional speed improvement.
Version 1.3.1
- E-mail option to automatically send you reports: add
--mail my@address.comto your command line. - Allow other database connections than SQLite3 by passing a connection string to the
--databasecommand line option. Examples:- SQLite3 file database:
--database filename.db(as before) - Connection URI:
--database postgresql://rla:rla@localhost/requests - ODBC-style:
--database adapter=mysql;username=root;host=localhost;database=requests - Memory database:
--database adapter=sqlite3;database=:memory:
- SQLite3 file database:
- Keep the previous database by default, pass the
--reset-databaseoption to clear the database before parsing. - Added an IRB console to inspect a request database just like Rails’s
script/console. Run withrequest-log-analyzer console -d <connection string> - Fixed some require paths that were causing problems.
Version 1.3.0
Retracted release
Request-log-analyzer 1.2 release cycle
Version 1.2.9
- Improved Apache access log format. Can now handle any kind of Apache access log file format by providing the
--apache-format <format>command line argument. - Allow
FileFormatsto be constructed dynamically (used for the Apache format implementation). - Refactored parameter passing during parsing to allow for more flexibility.
Version 1.2.8
Retracted release
Version 1.2.7
- Added Apache access log parser. To use, add
--format apacheto your command line invocation - Make the release script send the gem to RubyForge as well.
Version 1.2.6
- New, more robust gem release script using the ruby-git gem.
- Updated outdated information in the gemspec file
Version 1.2.5
- Improved Merb log format parser
Version 1.2.4
- More robust handling of database connections in database inserter.
Version 1.2.3
- Refactored database functions
- Cleaned up specs and tried some heckle
- Interrupts are handled more gracefully
- Moved munin tracker to a separate Github project
Version 1.2.2
Retracted release
Version 1.2.1
- Compressed logfile support
- Parsable YAML results as output (use
--dump <filename>command line option ) - Full Rdoc documentation
- Introduced Changelog
- Updated rails rake tasks
Version 1.2.0
- Ruby 1.9 support
- Rcov coverage (use
rake spec:rcovto generate the coverage report)






