Stephen Turner ([EMAIL PROTECTED]):
> On Fri, 18 Jan 2002, Aengus wrote: >> "Harry Lebowitz" <[EMAIL PROTECTED]> wrote: >> >> > Does anybody know if someone has written software to interrogate the >> > logfile, look at the entries in the logfile and create logformats >> > that I could choose to use in my analog.cfg ? >> >> Analog already does a pretty good job of looking at the entries in the >> logfile and creating a logformat - if it can't understand the logformat, >> it's likely to be because it's ambiguous, and a more aggressive aplication >> would be only marginally more successful anyway. > Hmmm, I'm not sure about this. Analog does a good job if the log is in one > of the standard formats. This includes cases where the header lines give the > format. But if it's in a custom format, analog doesn't even try. I think > there is scope for a program to try and be smart about this. For example, to > know that something of the form "Mozilla/n.m (stuff)" is a browser. I > suspect it's a hard job though. I agree. There is a lot more that could be done. It's not too hard to recognize IP addresses, requrest-like things, browsers, referrers, status codes (with enough lines), protocol, date and time, etc. I don't think it's too hard a job as long as the heuristics are right and there's enough data of the same format to be able to cover all the possible known cases. A Helper Application would be cool. A patch to Analog would be cooler! :-) -- Jeremy Wadsack Wadsack-Allen Digital Group +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
