Anne L. Noss ([EMAIL PROTECTED]; Thursday, June 12, 2003 9:30 AM): > Jeremy Wadsack wrote: >> Anne L. Noss ([EMAIL PROTECTED]; Thursday, June 12, 2003 8:48 AM): >> >> >>>I recently installed Analog 5.32, and am wondering if there's any way to >>>resolve what seems a fundamental problem. >> >> >>>I receive all my site's web logs in the form of email, which is >>>automatically forwarded to me by our Academic Technology department. I >>>have several years' worth of these emails, which I've been saving in the >>>hope of finding a tool which could analyze them. They are in a separate >>>folder on the personal drive made available to me by the University. >> >> >>>I've tried various approaches to editing analog.cfg's LOGFILE setting so >>>it could analyze these records. A basic path to the relevant folder >>>didn't work, as I suspected it wouldn't (but it never hurts to try the >>>easy way first!). So I saved one of the emails as a text file, changed >>>the extention to .log, and put it in a new folder. Then I revised >>>analog.cfg's line to LOGFILE F:\Stats\060103.log, to see if it would >>>analyze that one file. However, Report.html showed no results whatsoever. >> >> >>>Is there any way I can use Analog to generate an analysis of all these >>>saved emails? >> >> >> >> If the emails contain the log files as attachments, then you can save >> the attachments as separate files and Analog should be able to process >> them. Check the warning and error messages when it runs in case it has >> trouble with your log format. >> >> If the log files are the *content* of the emails you may have a >> problem. Likely the email system split the log file lines and you will >> have to come up with some way of recombining them. The best I can >> think of is a perl script, but you might be able to do it with >> VBscript as well. >> >> If the lines are not split then all you need to do is remove the >> headers from the emails. Again you could do this with a script. >> Alternately, you may be able to come up with some LOGFORMAT lines to >> tell Analog to ignore the headers and process the rest of the file. >> >> See http://analog.cx/docs/logfmt.html for details on the LOGFORMAT >> command.
> The log files are the content of the emails, and yes, the lines are > clearly wrapping in the mail display window. Yea, but are they wrapped in the original email? > I tried selecting the text from one of the emails, pasting it into > Notepad, and removing word wrap. That recombined the split lines. Then, > again, Good. What about that email file you saved as .log? If you open that with Notepad does it have the lines split or combined? > I saved the file with a .log extension and ran Analog...again, no > results. Check the error messages. Analog should tell you what's going on. Also look for "Corrupt lines" in the General Summary. If all the lines are corrupt, you can use Analog's "DEBUG C" command to have it tell you where in the process it's failing to read the lines. If you can't figure out the LOGFORMAT and it's not a default one, you can post 3-5 lines (no more) to the list and we can try to help you. However, if the lines are split in the actual email, then that's the problem and you'll have to look at other methods of recombining them. > The content of the emails begins with: > Top 10 paths accessed: Uh.... that sounds like a report. Not a log file. > and ends with: > ----- END ERROR LOG ----- And you don't need to process the error log. That's meant for human consumption. All the information Analog gathers from the access log. -- Jeremy Wadsack Wadsack-Allen Digital Group +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
