Support for analog web log analyzer <analog-help@lists.meer.net> wrote:
< As for your options, you could either edit your logfiles to change < these two things, or you could write your own LOGFORMAT instead of < relying on analog parsing the #Fields line. I posted a LOGFORMAT on Friday, but my server seems to have difficulty delivering mail to this list in the last few weeks - it's reporting that it can't find an MX record for lists.meer.net. Anyway, here's an excerpt from the e-mail that bounced over the weekend: You can use an explicit LOGFORMAT to tell Analog how to parse your logfile by adding these lines to your analog.cfg file: LOGFORMAT (%Y-%m-%d %h:%n:%j %T %S %c %j %b %j %j %j %v %r %q %u %j"%B" %j"%f") LOGFORMAT (%Y-%m-%d %h:%n:%j %T %S %c %j %b %j %j %j %v %r %q %u %j"%B" %j) LOGFILE logfile.log I added 2 lines, the first for when there are referrers (I assume your webserver is quoting the referrers), and one for lines without referrers. Analog will use whichever one matches each line of the logfile. Note that there is no space between the between the %j and "%f" at the end of that first line. Aengus ----------------------------------------------------------------- Find the home of your dreams with eircom net property Sign up for email alerts now http://www.eircom.net/propertyalerts +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------
