Did you read the FAQ item that I linked to? That's the double counting
I'm talking about.

-- 

Jeremy Wadsack
Wadsack-Allen Digital Group


Michael Rabe ([EMAIL PROTECTED]):

> Thanks for the feedback - could you elaborate on the "double counting"?
> What is that potential?  A lot of the redirects I see correspond to POSTS
> to a servlet (which appears like a directory in the Url field of the log)


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jeremy Wadsack
> Sent: Friday, March 22, 2002 2:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [analog-help] Can Analog handle Redirects as Requests?



> Michael Rabe ([EMAIL PROTECTED]):

>> Is there any way to break down Analog's Redirects report into the Monthly,
>> Daily,
>> and Hourly summaries as it does for the Requests?

>> I would like to filter on log entries using FILEINCLUDE and REFINCLUDE
>> config
>> entries, but it seems that analog does not include a redirect as a
> request.

>> Ideally, if every entry was treated as a request, I would be fine.  But,
> to
>> my
>> knowledge, Analog is too smart and treats all the entries with HTTP 300
>> status codes as redirects.

>> My current workaround is to use "sed" to change all the "300" status codes
>> into 200s, then run the appropriate Analog reports.

>> Any thoughts on this?

> http://www.analog.cx/docs/faq.html#faq181

> If you are ok with the potential double counting on directories, then
> your sed approach is probably the best.


> --

> 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
+------------------------------------------------------------------------

Reply via email to