use strict;
use warnings;

use Parse::RecDescent;
use Data::Dumper;

my $g = Parse::RecDescent->new(<<'EOG');
main: head row(s) /\Z/ { [$item[1], @{$item[2]}]; }
 | <error>
head: /.*/ /-*/ { $item[1]; }
row: date time num { [@item[1..3]]; }
date: /\d\d\d\d-\d\d-\d\d/ 
time: /\d\d:\d\d:\d\d/
num: /[\d\.]+/
EOG

my $data = join '', <DATA>;

print Dumper($g->main($data));

__DATA__
Timestamp 10.72.218.82:cpu_busy
----------------------------------------------------------------------
+--------- 
2009-11-05 17:59:52 1.501
2009-10-15 17:39:52 2.501
2009-12-25 17:19:52 3.501

[download]
will return the following, skipping empty lines and spaces, or generate a detailed error if data is invalid. 
$VAR1 = [
          'Timestamp 10.72.218.82:cpu_busy',
          [
            '2009-11-05',
            '17:59:52',
            '1.501'
          ],
          [
            '2009-10-15',
            '17:39:52',
            '2.501'
          ],
          [
            '2009-12-25',
            '17:19:52',
            '3.501'
          ]
        ];

[download]
Update: changing the row: rule returning a DateTime will also verify if the date is correct, improving the error detection while parsing.

In reply to Re: Better way to perform "double split" ? by oha
in thread Better way to perform "double split" ? by perlpal

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.