Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I would consider a brute force method to begin with and then refactor from there. Here's where I'd start:

First, you need to decide how to start the processing:

  • Begin at a point where all partitions are quiet?
  • Accept the fact that some jobs may have already started when you begin and either ignore them or check the RC and report accordingly (don't worry about start information)?

I'd parse the log file line by line and use a hash to keep the necessary info for the jobs in progress:

$jobs{$partition}{jobname} $jobs{$partition}{starttime} $jobs{$partition}{endtime} $jobs{$partition}{rc}

You examine each line and determine:

  • Is this the beginning of a new job? If so, store jobname, starttime.
  • Is this the end of a job? If so, have I recorded the start info for this job? if so, store endtime, rc, report, delete entry.
  • Ignore if neither of the above is true

Determine your strategy for what happens when you reach EOF:

  • Ignore the jobs started but not finished (or at least report that fact with the data you have)?
  • Choose an ending point in the log file where the partitions are all quiet?

The regexen used to parse each line should be fairly straight forward, you only have to read the file once, and you keep storage to a minimum. Would this be the most efficient way to do it? I don't know but as I said, during the coding process, you may gain some insight to try something different.

--Jim


In reply to Re: Daily Log Audit (regex issue) by jlongino
in thread Daily Log Audit (regex issue) by blacksmith

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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 or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (3)
As of 2021-12-05 23:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    R or B?



    Results (31 votes). Check out past polls.

    Notices?