[Web4lib] web log analysis tool

[Jennifer Ward]

One thing to consider in all of this is site size and how much data you 
want to see. We were using Wusage for a number of clustered websites and 
the parsing process would bring the server down every time it ran. We're 
moving to Urchin (http://www.urchin.com), which seems to be more robust, 
easily configured, and isn't too expensive (although after seeing 
Blake's response, I guess that depends on your perspective).

Cheers,
Jennifer

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jennifer Ward
Head, Web Services
Information Technology Services
University of Washington Libraries
phone: 206.685.3121
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cashatt, Mark wrote:
> We have been using wusage http://www.boutell.com/wusage/.  The price is
> right. Configuration is a little rough (web form based with ascii macros
> to edit canned text content).  Not the flashiest of apps, but does a
> pretty good job of displaying useful web data.
> 
> 
> Mark Cashatt
> California State Library
> 916.653.4273
> mcashatt at library.ca.gov
> 
> 
> 
> -----Original Message-----
> From: web4lib-bounces at webjunction.org
> [mailto:web4lib-bounces at webjunction.org] On Behalf Of Maceli,Monica
> Sent: Monday, May 23, 2005 11:38 AM
> To: web4lib at webjunction.org
> Subject: [Web4lib] web log analysis tool
> 
> Hi,
> 
> I'm looking for recommendations for web log parsing and analysis. From
> what I've seen there seems to be a big gap between what some of the
> free/open source options provide (ie - analog, webalizer, awstats) and
> what the commercial versions (webtrends, urchin) offer.  For our
> library, the commercial versions seem to be more than we need but the
> open sources ones might not have enough (ie might have to do work on top
> of them to get all the features we want). Just wondering if anyone had
> any recommendations or suggestions?
> 
> Thanks!
> 
> Monica Maceli
> Webmaster, W. W. Hagerty Library
> Drexel University
> monica.maceli at drexel.edu
> 215-895-1344