comment on

Your data seems a bit too ambiguous to parse easily. You can't, as in your example, just split on white space, as your 'msg' data field is an unquoted string (so you'll get a seperate field for each word in the string). Your best option is to get the log file tab delimited (I'm guessing it isn't at the moment), and stop reading this post.

However, if you don't have control of the data, you'll just have to take a stab. With the assumption that the first four fileds don't have spaces in them, and that the key/value data that follows doesn't have any '='s in the data, then you could do something like this...

#!/usr/bin/perl
use Data::Dumper;

while(<DATA>) {
    chomp;
    my ($log_date, $log_time, $something, $ip_address, $keyed_data_str
+ing ) = split /\s+/, $_, 5;

    my %keyed_data_hash;
    while( $keyed_data_string =~ s/\s*(\w+)=\s*([^=]*)$/ $keyed_data_h
+ash{$1} = $2; ''/xsge) { 1 }


    print Dumper($log_date, $log_time, $something, $ip_address, \%keye
+d_data_hash);

}

__DATA__
2007-11-16 16:05:40    Local1.Alert    128.2.2.40    id=firewall time=
+"2007-11-16 16:03:37" fw=WS2000-Store 02 pri=1 proto=6(tcp) src=128.2
+.2.200 dst=128.2.100.106 mid= 1013 mtp=  2 msg=TCP connection request
+ received is invalid, dropping packet Src 23 Dst 4631 from EXT n/w ag
+ent=Firewall
[download]

OUTPUT

$VAR1 = '2007-11-16';
$VAR2 = '16:05:40';
$VAR3 = 'Local1.Alert';
$VAR4 = '128.2.2.40';
$VAR5 = {
            'msg' => 'TCP connection request received is invalid, drop
+ping packet Src 23 Dst 4631 from EXT n/w',
            'proto' => '6(tcp)',
            'time' => '"2007-11-16 16:03:37"',
            'src' => '128.2.2.200',
            'mtp' => '2',
            'mid' => '1013',
            'fw' => 'WS2000-Store 02',
            'agent' => 'Firewall',
            'id' => 'firewall',
            'pri' => '1',
            'dst' => '128.2.100.106'
        };
[download]

... which works by pulling off the easy four first fields, and then works from the end of the rest of the data, creating a key pair hash.

It's pretty ugly, but with your data, I don't see a way around it.

---
my name's not Keith, and I'm not reasonable.

In reply to Re: Parsing a log file by reasonablekeith
in thread Parsing a log file by TStanley

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, 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, 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:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.


"be consistent"
	PerlMonks