RE: Remote and local statistics

If it helps explain my situation at all, here is a test results page I have
been working on

http://proxy.dupagels.lib.il.us/ob_proxyStats.html


  

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Brian Clanton
> Sent: Tuesday, August 12, 2008 5:04 PM
> To: 'Support for analog web log analyzer'
> Subject: RE: [analog-help] Remote and local statistics
> 
> I believe my situation is a little different in that the Proxy server
> (EZPROXY) that our library clients are using creates special 
> log files that only track when the database link is clicked on.
> 
> For instance, when a patron clicks on the link on the 
> libray's website, Ezproxy only creates ONE log and that entry 
> is either a 200 remote or a 301 response.
> 
> Unless of course I am mistaken about this, but this is what 
> it looks like is happening in the log file.  Here are a few 
> log examples of from a LOCAL ip address that is accessing 
> different GROLER database: 
> 
> local 66.158.45.2  - - [12/Aug/2008:14:45:05 -0600] "GET 
> http://atb.grolier.com/ HTTP/1.1" 301 467 local 66.158.45.2  
> - - [12/Aug/2008:14:45:22 -0600] "GET http://gme.grolier.com 
> HTTP/1.1" 301 465 local 66.158.45.2  - - 
> [12/Aug/2008:14:45:41 -0600] "GET http://lp.grolier.com 
> HTTP/1.1" 301 463 local 66.158.45.2  - - 
> [12/Aug/2008:14:46:06 -0600] "GET http://ea.grolier.com/ 
> HTTP/1.1" 301 465 local 66.158.45.2  - - 
> [12/Aug/2008:14:46:54 -0600] "GET http://atb.grolier.com/ 
> HTTP/1.1" 301 467 local 66.158.45.2  - - 
> [12/Aug/2008:14:47:05 -0600] "GET http://ea.grolier.com/ 
> HTTP/1.1" 301 465 local 66.158.45.2  - - 
> [12/Aug/2008:14:47:16 -0600] "GET http://gme.grolier.com 
> HTTP/1.1" 301 465 local 66.158.45.2  - - 
> [12/Aug/2008:14:47:29 -0600] "GET http://lp.grolier.com 
> HTTP/1.1" 301 463
> 
> These are the last logs of the day today and as you can see, 
> no additional logs are generated once the log has been 
> redirected.  If you are familiar with Ezproxy the logformat 
> command within the Ezproxy config file is:
> 
> LogSPU  spu.log %{ezproxy-spuaccess}i %h  %l %u %t "%r" %s %b
> 
> This log file format allows for differentiating between local 
> and proxy logs, which the libraries want statistics for.
> 
> Anyway, to me it seems I need to include the redirected logs 
> since these are the only accounts of local access requests 
> from patrons that are in the log file.
> 
> Am I correct in saying this?  
> 
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of Aengus
> > Sent: Tuesday, August 12, 2008 4:34 PM
> > To: Support for analog web log analyzer
> > Subject: Re: [analog-help] Remote and local statistics
> > 
> > Brian Clanton <[email protected]> wrote:
> > > The problem is that the proxy server (Ezproxy) redirects 
> the local 
> > > access requests (301) to save on bandwidth and only "proxies" the 
> > > remote requests. Therefore Analog only shows stats for the 
> > > "successful" proxied requests in the other subsequent
> > reports, namely
> > > the REQUEST REPORT.
> > > 
> > > Is there a way to configure Analog to consider all requests, both 
> > > local and proxy, as legitimate requests so the REQUEST 
> REPORT will 
> > > show totals for both local and remote patrons as well still  have 
> > > separate reports showing total remote requests (User
> > Report) and total
> > > local requests (REDIRECTED USER REPORT)for a given time period?
> > 
> > The issue of treating 301's as Successful requests is delat with in 
> > the Analog FAQ:
> > http://analog.cx/docs/faq.html#faq181
> > 
> >   I want to be able to count requests with status code 301 and
> >   302 as successes, so that they appear in the Request Report. 
> > 
> >   No, you really don't, because that would lead to double counting
> >   when a request for /dir (code 301) is redirected to /dir/ (code 
> > 200).
> >   For CGI scripts etc. look in the Redirection Report instead of the
> >   Request Report. 
> > 
> > 
> > If you want all the entries to turn up in the Request Report, then 
> > you'll have to modify the Response Code to be 200.
> > 
> > Aengus
> > 
> > +-------------------------------------------------------------
> > ----------
> > +-
> > |  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
> > +-------------------------------------------------------------
> > ----------
> > +-
> > 
> 
> +-------------------------------------------------------------
> ----------
> +-
> |  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
> +-------------------------------------------------------------
> ----------
> +-
> 

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