Fellow Monks,
Consider the following log file entry: 

Aug 22 11:46:27 masterudp003210uds.netops.msnyuhealth.org 148526: Aug 
+22 15:46:26 UTC: %SEC-6-IPACCESSLOGDP: list 101 denied icmp 10.4.12.2
+53 -> 10.7.151.48 :8/0:, 1 packet

[download]
Following the advice of my fellow monks I broke up my regexes using qr and came up with this list of regexes: 
my $dtg=qr@[A-Z][a-z]+\s\d+\s\d+:\d+:\d+@;
my $thingy=qr([\.\d]+);
my $tz=qr([A-Z]{3});
my $ipaddr=qr@\d+\.\d+\.\d+\.\d+@;
my $fqdn=qr@[a-zA-Z\-\.]+@;
my $timezone  = qr@[A-Z]+@;
my $fragger = qr@(\%SEC-6-IPACCESSLOGP|\%SEC-6-IPACCESSLOGDP)@;
my $list=qr@list\s(\d+)@;
my $protocol = qr@(tcp|udp|icmp)@;
my $ip_with_port=qr@($ipaddr):(\d+):@;
my $arrow = qr @\-\>@;
my $time_lapse=qr@\d+d\d+h@;   # Something like 6d45h <sigh!>
my $metric_ex=qr(\d+:);
my $dtg1="Aug 22 11:46:27";
my $month="Aug";
my $monthDay="Aug 22";
my $time="11:46:27";

my $matchMonth=qr([A-Z][a-z]+);
my $dateMatch=qr($matchMonth\s\d+);
my $matchTime=qr(\d+:\d+:\d+);

[download]
No doubt there are useless lines up there as I cut and pasted this from some unit testing that I was doing. So far so good.. right? well... here is a test sniglet that I wrote: 
printf "Full String: %s\n",(
                           $full_string =~ m@
                           ($dateMatch\s$matchTime)\s
                           ($fqdn|$ipaddr)\s
                           $metric_ex\s
                           ($dateMatch\s$matchTime)\s
                           ($timezone):\s
                           $fragger:\s
                           list\s(\d+)\s
                           denied\s($protocol)\s
                           ($ipaddr)\s
                           $arrow\s
                           ($ipaddr)\s
                           :\d+\/\d+\:,\s
                           (\d+)\spacket
                           @x
                           ?
                           "OK":"FAILED"
                           );

[download]
It fails to match... Anyone have an idea why?

A very tired cattle dog style Perl Monk going to bed now.

Peter @ Berghold . Net

Sieze the cow! Bite the day!

Nobody expects the Perl inquisition!

Test the code? We don't need to test no stinkin' code!
All code posted here is as is where is unless otherwise stated.

Brewer of Belgian style Ales

In reply to CISCO Log file pattern matching (again!) by blue_cowdawg

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.