RSS | Module Info | Add a review of Apache-ParseLog

Apache-ParseLog (1.02)

The module didn't have the ability to do some key things I needed it to (use a very complex httpd.conf, or otherwise be able to directly specify the location of a custom log file; be able to parse only the tail end of the log file rather than the whole two year's worth).

I won't complain about free code, but as Peter mentioned, the author didn't seem to be very familiar with using all the features that Perl provides (customlogDefined()+customlog() is a poignant example... both functions could be replaced with a simple hash lookup).

Though here's a workaround for parsing a combined log from an arbitrary path if you poke inside $self:

$parselog->{customlog}{location}{combined} = '/path/to/the.log';
$parselog->{customlog}{nickname} = [qw[ combined ]];

For alternatives, see:
- Logfile::Access
- http://www.oreilly.com/catalog/perlwsmng/chapter/ch08.html
- the Regexp::Log:: set of modules
- HTTPD::Log::Filter
- AWStats' awstats.pl (search for "Start Update process"... the code isn't very modular though)
- http://www.fourmilab.ch/fourmilog/archives/2005-03/000500.html

David Newcum - 2007-10-31 12:14:21
Was this review helpful to you?  Yes No

Apache-ParseLog (1.02)

The documentation is extensive but unfortunately is missing some very important details like for example how to handle CustomLog's if you dont want to use the "parse a httpd.conf" interface.

The code quality probally speaks for it self. The config methods declaration of a list of variables and then using a set of variables named not quite the same is a minor issue. The getCustomLog method is recommended reading, quite a WTF.

Peter Makholm - 2007-09-05 06:23:36
Was this review helpful to you?  Yes No

Perl.org sites : bugs | dev | history | jobs | learn | lists | use © Copyright 2002-2010 The Perl Foundation Site Information and Contacts root: (Vh | Vc)