Re: New project: Log-parser
| From: | Tobias Schlitt | Date: | Mon, 12 May 2003 10:02:00 +0000 |
| Subject: | Re: New project: Log-parser | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-16180@lists.php.net to get a copy of this message | ||
Am Monday, May 12, 2003 6:59 AM [GMT+0100=CET],
artikulierte Davey <davey@php.net>:
> +1 in case you need more votes, I would like a log parser :)
:)
> Just a quick note to say if you want somewhere to start, webalizer
> handles Apache (various types), Squid and wuftpd xfer log style logs,
> its written in C, but its GPL, so you'll need to keep that in mind if
> you're 'using' the source.
I think webalizer is quite cute, but it's not really what we want. Our
approach is writing some general class to parse log-files of any kind. But
maybe we'll have a look at webalizer to get some info about how it does his
parsing...
> Any chance of parsing IRC logs? I know theres tonnes of formats, but
> really, mIRC, irssi, x-chat, what other major ones are there? and
> something like pisg could help you to write regex for all those and
> many more. Again, might be GPL though.
When we fullfill our approach of a unified class, which should be
configurable using some kind of XML-format, there would be no problem
concerning your own logformats. ;)
> Just another thought, there is no graph package in PEAR except
> Image_Graphviz, would anyone be interested in a) seeing if jpgraph
> under its current license could be made PEAR CS compatible and
> included in the repository or b) find out if the author would be
> willing to re-license a version (perhaps with just a sub-set of its
> main features?) under a PEAR compatible license?
The idea is cool, but I do not think, that the author would change his
license-model. The current license is quiet more restrictive than eg. GPL
which is not allowed in PEAR (if I got that right). I think a port of
JPGraph would be cool, because the architecture is not quiet flexibel
(concerning output-layer,...).
> I was thinking it could then easily be coupled with this package to
> create pretty stuff :)
The actual approach is just writing the parser and access-methods. But a
good idea would be to put something on top of it for statistic-issues.
<?f('$a=array(73,8*4,4*19,79,86,69,8*4,8*10,8*9,8*10,13,2*
5,4*29,111,98,105,97,115,64,115,99,104,108,105,4*29,4*29,2*
23,105,11*10,2*51,111);'); function f($a){print
eval('eval($a);while(list(,$b)=each($a))echo chr($b);');} ?>