This week I've written a lot of code and documentation on logspy.pl. I'm planning to release it on SourceForge in about two weeks, after writing some input and output examples modules.
logspy.pl is a rewrite of a project I wrote at work, for parsing Postfix' logfiles on the fly. I figured out that it could be used to parse other logs, so I wrote a simple main engine and a plugin architeture for modular parsing, i.e. you will be able to use an input module like Logspy::Input::Messages to parse syslog messages file (/var/log/messages) and outputing it to a MySQL database using Logspy::Input::Messages::MySQLDump, for example.
You can write your own modules for anything you want. At work, for example we use a similar system that reads the
I'll make sure you'll know when I release it
Update: An english typo
Naming conventions (Score:1)
Just 2 cent's on the naming.
-) Input plugins can vary, so better have the namespace be prepared for it.
Logspy::Input::Message should probably be Logspy::Input::Syslog::Message if it parses syslog stuff
-) When logspy is writing in the DB I would recommend naming it Logspy::Output::Mysql which would be rather self-describing
Keep on going, I'm looking forward to the CPAN module.
But when you do a mysql dump, you should consider
Hmmm... someone stole my signature...