This code matches the line of keys (ticket, customer, etc), and then continues stuffing lines into the summary field until it matches another line of keys. The part of the regex that matches the ticket # will probably need to be changed, and you might want to think about what kind of whitespace you'll end up with in your string when you have a multi-line summary.
#!/usr/bin/perl -w
use strict;
use Data::Dumper;
my %record;
my $summary_flag;
while(<>) {
print;
if (/(fabx-t\d+\:) \[(\S+)\] \[(\S+)\] \[(\S+)\] \[(\S+)\]/) {
# Print the previous record.
print Dumper(\%record);
# start a new record hash
%record = ( 'ticket#' => $1,
'customer' => $2,
'status' => $3,
'priority' => $4,
'owner' => $5 );
} else {
$record{summary} .= $_;
}
}
# print the last record
print Dumper(\%record);
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|