comment on

Your boss doesn't seem to have given you a formal statement of requirements. That's good news for you: it means you're needed.

Take a reasonable sample of your data (perhaps slightly larger than you posted here) and manually transcribe it as a CSV file. You will start to notice you have some choices to make.

Do you want to keep all the data you see? You've told us you don't. So you probably have a finite list of fields to be recorded. Put that list in your column headings.

A first approximation to your column headings might be Timestamp, LoadAvg1, LoadAvg2, LoadAvg3, SleepingProcesses, RunningProcesses and whatever else you know to be of interest.

Alternatively, your boss may want a taller, narrower list containing dated name-value pairs. Your guess is better than mine.

Give the boss your manually transcribed CSV file and ask "Is this what you need?"

If the answer is yes, the rest is a simple matter of programming.

In reply to Re: Parsing a non-formatted record text file by Narveson
in thread Parsing a non-formatted record text file by TStanley

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.


P is for Practical
	PerlMonks