Steven Turner wrote:
> I guess I'm asking if there is a "canned" LOGFORMAT better than the one I
> wrote, because I figure that is, at least, part of the problem.
Well, the LOGFORMAT you sent before was fine for your sample logfile line.
So I suspect what is going on is that you have lines in lots of different
formats in the same logfile?
Without ranging too far afield, I grabbed (cat xferlog | head >
/tmp/xferlog) the top few lines and ran analog against them. I wasn't date
specific (as in generating a last 7 day report). I dumped the FILEEXCLUDE
declaration, got rid of the FROM and TO directive, and changed the LOGFILE
pointer. What I got, in the form of a report, was:
Program started at Tue, Jan 12 1999 11:18.
Analyzed requests from Fri, Sep 18 1998 01:59 to Mon, Sep 21 1998
11:09 (3.4 days).
-----------------------------------------------------------------
General Summary
---------------
Successful requests: 10
Average successful requests per day: 2
Distinct files requested: 7
Distinct hosts served: 2
Data transferred: 2,761 kbytes
Average data transferred per day: 836,067 bytes
...
So, a general report was created for these entries:
Fri Sep 18 01:59:39 1998 4 prfbank1-dawn1.ll.relcom.ru 304
/pub/incoming/CUTEFTP.INI b _ i a [EMAIL PROTECTED] ftp 0 *
Fri Sep 18 02:02:22 1998 5 prfbank1-dawn1.ll.relcom.ru 304
/pub/outgoing/CUTEFTP.INI b _ i g elektron ftp 0 *
Fri Sep 18 02:03:20 1998 1 prfbank1-dawn1.ll.relcom.ru 304
/pub/outgoing/CUTEFTP.INI b _ o a [EMAIL PROTECTED] ftp 0 *
Fri Sep 18 02:16:10 1998 4 prfbank1-dawn1.ll.relcom.ru 304
/pub/outgoing/CUTEFTP.INI b _ i g elektron ftp 0 *
Mon Sep 21 10:55:55 1998 63 195.243.100.186 528384 /pub/outgoing/Cnet.pdf b
_ i g elektron ftp 0 *
Mon Sep 21 10:56:50 1998 25 195.243.100.186 147456 /pub/outgoing/Cnet.pdf b
_ i g elektron ftp 0 *
Mon Sep 21 10:58:07 1998 66 195.243.100.186 483855 /pub/outgoing/e200.exe b
_ i g elektron ftp 0 *
Mon Sep 21 11:07:37 1998 121 195.243.100.186 853121
/pub/outgoing/FTP_CNET/DRIVERS/e100tx.exe b _ i g elektron ftp 0 *
Mon Sep 21 11:08:46 1998 67 195.243.100.186 483855
/pub/outgoing/FTP_CNET/DRIVERS/e200.exe b _ i g elektron ftp 0 *
Mon Sep 21 11:09:31 1998 43 195.243.100.186 329646
/pub/outgoing/FTP_CNET/DRIVERS/e40bc.exe b _ i g elektron ftp 0 *
but the rest gets a bit fishy, and I may be expecting something from the
log
file that I'm not entitled to view:
Monthly Report
--------------
Each unit (+) represents 1 request for a page.
month: pages:
--------: -----:
Sep 1998: 0:
Does this mean I can't "fool" analog into seeing the downloads a
pages, so I can't get a day to day report, much less generate a report that
shows how many of what was actually "hit" since this is the kind of
thing that pops out:
Daily Report
------------
Each unit (+) represents 1 request for a page.
date: pages:
---------: -----:
Sep/18/98: 0:
Sep/19/98: 0:
Sep/20/98: 0:
Sep/21/98: 0:
And, finally, is there an upper limit to the number of "corrupt" entries
analog will deal
with before just giving up. That is, despite the "corrupt" entries, there
is valid
data for the time period in question, but even analog's general summary
says
zilch was transfered.
--------------------------------------------------------------------
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.
--------------------------------------------------------------------
