Statistical Analyzers for HTTP Logs?
krishnaD asks: "I have been using webalizer to generate access
log reports for the site but lately my customers
are asking for statistics like average amount of time spent by visitors on site, if a person reaches a page X, what is the probability that from here he goes to Y? From which link people exited the site etc. Basically, they are asking for a detailed flow analysis of usage patterns of visitors. Are there any tools that will do this kind of analysis? I love to know what kind of tools other sysadmins use to generate reports for their clients."
Freshmeat Internet::Log Analysis
I have tried webalizer and webtrends, but without a doubt, nr. 1 is Urchin. It really is the cream of the crop, but it costs too. You check out a sample here.
If you get an account with Verio, you will get your stats in Urchin for free.
Hurra for Knark!
Access Analyzers (Uppsala University)
Log Analyzers (reallybig.com)
Web Log Analyzers (2K Communications)
If I weren't nailed to the penis, I'd be pushing up the daisies!
I've used WebTrends for about a year, and couldn't be less impressed. Randomly chokes on logs that webalizer handles without trouble. Hard-to-use interface. Reports a number of things that you really can't tell from web logs.
On the plus side, the PHBs love it.
Well, if you are looking for free stuff...
/index.html
:-)
I'd recommend W3Perl http://www.w3perl.com/softs/index.html which is a kind of mess of perl scripts, but is surprisingly fast (much faster than other perl-only stats packages), and is the most full featured free package I've ever come across.
Set up is kind of a pain - it's rather complex, owing to the vast array of configurable thingies, but it works pretty well once it's put together.
There are some genuinely innovative features, such as a tree view of your website weighted by the popularity of each branch from
Worth a look if you are on a feature hunt. It requires some arcane image generation program to make the pretty graphs.
Oh, and if you were hoping to explore the code - be aware that the guy who wrote it is French
-----
But you cannot tie a particular IP address to a user. You have the problems of AOL users (each request from a different IP address) and corporations (and now many homes) using NAT or PAT devices to make 1 or more users have the same IP address.
The best way to get around this is setting a session cookie via Apache. Then you key off that.
The program isn't debugged until the last user is dead.