I wrote a generic log-reader combined with a custom query language (looked like SQL, and I based it on Parse::RecDescent) several years ago. It supported reading fields from comma(or anything else)-separated records, regex-separated records, or a custom regex. Once an object was defined, each read would return an array wanted fields from the next line, that were fed to precompiled query for evaluation.

I don't have the code handy, but this solution can be abstracted very nicely. One gotcha is that it was quite slow, esp. if regular expressions were used to extract values from each line (I'm talking hundreds of megabytes of logs).

In reply to Re: Re^4: Runtime Regexp Generation (I agree, but...) by dmitri
in thread Runtime Regexp Generation by tekkie

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.