On Thu, 3 Dec 1998, Aengus Lawlor wrote:
>
> One of the advantages of the Extended Log format is that it can be
> smaller, because it doesn't include redundant information. (The same 10
> byes of Date information occur on every single line. It's only 10 bytes
> per line, but for compact logs, that might represent 15%-30% of the log
> size). It seems to me that it would be reasonable for Analog to assume
> that if I choose to leave out the date field, that I did it for a
> reason. While it would be nice to have Analog recognize Date changes in
> mid stream by recognizing new #Date fields, it would also be perfectly
> reasonable to say that you will only handle one date per file, and
> require a seperate logfile for each date.
>
Well, I agree, and I probably will end up doing something like this. I'm
still not sure what to do if the date flips over from 23 to 00 without a
new #Date line though. Or from 23 back to 22?
> I have 30 Extended Daily Log Files for the month of November. Can I
> easily analyze them all at once by specifying a custom LOGFORMAT, or
> will I have to create a config file specifying a start date for each
> daily log file?
>
You can define a LOGFORMAT in which the time fields are %j'unked, but you
will lose the date/time information. Alternatively you can preprocess the
logfile before passing it to analog. Neither solution is ideal.
--
Stephen Turner [EMAIL PROTECTED] http://www.statslab.cam.ac.uk/~sret1/
Normally: Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
Until 12/98: Dept of Math & Stats, 585 King Edward Ave, Ottawa K1N 6N5, Canada
Microsoft: Where am I allowed to go today?
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------
