We have various log files, and perl helpfully outputs error messages into them. We'd like to be able to figure out which lines we should get upset about. For example, "^Undefined subroutine in sort". Once I know this is a problem, I can (for example) email someone when this shows up in my logfiles.

So I took the perldiag 5.8.8 manpage and made a list of all 676 errors (noting that several that I've seen aren't on this list), made regexes to recognize them, built a test suite, and then thought to myself, "Self, has someone done this?", followed by "Self, this is kinda lame, surely there's a better way?"

I'm happy to make a cpan module if there isn't one. Or tell me, is there a better way? I mean, dozens of daemons running on hundreds of nodes can't be simple, but this is ridiculous.

In reply to Parsing perl errors by wumpus

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.