I'm trying to setup analog to process our NT 4.0 / IIS 4.0 log files in
Extended format. The log file headers contain the proper field
specifiers and Analog appears to recognize the file type - it states it
as:
Current logfile format:
#Fields:<W3 extended format string>\n
#%j\n
However, all the lines in the file end up becomming corrupt lines, and
the report has no requests. I've tried specifying it with LOGFORMAT
EXTENDED and LOGFORMAT with a format string, but I get all corrupt lines
either way.
Until a week ago we were processing the log with an in-house perl script
that had no problem matching the Extended format field spec to the
logfile lines.
Any clues as to why Analog is having problems doing this?
TIA,
Jeremy Wadsack
The Flagstaff Link
http://www.flagstaff.net/
--------------------------------------------------------------------
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.
--------------------------------------------------------------------
