From owner-freebsd-isp Wed Jun 21 5:36:46 2000 Delivered-To: freebsd-isp@freebsd.org Received: from federation.addy.com (federation.addy.com [208.11.142.20]) by hub.freebsd.org (Postfix) with ESMTP id 4910137BE21 for ; Wed, 21 Jun 2000 05:36:44 -0700 (PDT) (envelope-from jim@federation.addy.com) Received: from localhost (jim@localhost) by federation.addy.com (8.9.3/8.9.3) with ESMTP id IAA43937 for ; Wed, 21 Jun 2000 08:36:42 -0400 (EDT) (envelope-from jim@federation.addy.com) Date: Wed, 21 Jun 2000 08:36:42 -0400 (EDT) From: Jim Sander Cc: freebsd-isp@FreeBSD.ORG Subject: RE: Web tracking software In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > ** What suggestions do y'all have? Horror stories? Good products? We run Analog (http://analog.cx/) with great success. We *used* to run WebTrends on a dedicated NT box. Definitely a horror story- that one machine gave us more trouble than the 10 BSD servers it was analysing reports for. That's probably as much MS's fault though. Still, after more than a year listening to their support staff tell me that I needed more memory and more processor (despite the fact that neither was being heavily used) I finally got in contact with a real programmer there who told me basically "Yeah, real-time analysis has some bugs- turn it off" which of course fixed the problem, while removing the greater part of the functionality I needed. WT reports tend to track things that simply are not reliable (click-path and the infamous "user session" concepts) and does a questionable job at even that. Comparing a WT generated report to an analog report (or a grep -c on the raw log) yielded a lot of unexplainable differences. My personal advice is to avoid webtrends like the plague- it may work for some situations, but definitely not the one I'm in. -=Jim=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message