Welcome to WebmasterWorld Guest from 22.214.171.124
Things I would like, in addition to the norm:
* session tracking
* most productive kws/SEs - (which kws/SEs generate longer sessions) <-- may be asking a lot
* keywords by SE (inclusive of top 8-10 engines, possibly configureable)
* keywords overall
* current (and hopefully updateable) robots/spiders visit tracking
* unique visitors by hour/day/week/month
* relatively simple to configure
* dl'd logfile stored in sequential dirs/filenames
* reports generated in sequntial dirs/filenames
Anyone know a reliable proggy to do this? Am I asking for too much?
Also, regardless of above features, what's your favorite?
It does everything, and more, that you mentioned above, and it does it well.
I can't really say that it is my favorite as I haven't used any others yet. I would like to hear of some others that have given good results though.
I use the free software "Webalizer" to track our logs, though it doesn't do some of what is looked for here (like tracking spiders, though they do show up in other ways...)
I haven't used the latest version of Webalizer, and it may do these things now. It can be found at [mrunix.com...]
For tracking our internal website I use an application called SurfStats, which wasn't free, but a good deal less then WebTrends. It has some annoying quirks, but it does get the job done. The downloaded log files are stored in a db, however.
I am running about 20-30 reports on the server, so if we were running 3 or 4 reports for each of the 20-30, I think that the server would have a fit. I don't even think the guys in that department would even permit me to do that.
Have you had any problems like this, or am I wrong about it eating up the server?
NetTracker Pro, on the other hand, is impressive in its drill-down capability. You can start at the 50,000 foot level and drill all the way down to looking at an individual visitor's path through your site. Custom reports are fairly easy to create and save for automatic generation. Exporting data for analysis in Excel or Access is quick and easy.
FastStats is one I haven't used in a while. It is really fast, but the reporting has some limitations that made me discard it.
One other factor when you are looking at pricing - be sure to check how multiple domains are handled. Neither WebTrends nor NetTracker are unlimited use programs. Each software vendor has their own approach to handling more than one domain, and you should be sure you price out all the options.
But I am soon to turn completely to Network Package Sniffing instead. I am working with a local company that have made a box that can sniff and produce true live stats for me like nothing I have ever seen before. It is amasing. I can get all the numbers I want in TRUE realtime (No delay at all beside the time it takes to refresh the stat page).
I am working with the company to design new reports. In the first version of the box it will just be standard reports (like WT) but in the second edition users can set up their own reports. If you have ANY ideas of what kind of reports you - as SEO's - want then let me know, and I have them made :)
Besides the real time stats there is a number of reasons that I turn to Network Sniffing away from Server Monitor Logs.
1) It is much easier to set up and maintain. I (or my clients) save costs here.
2) When using Network Sniffing I can turn off logging on the server. Testing have proved that NT takes about 20% of the recourses to do logging and 15% on Apache. That is A LOT of power to save. In a cluster with 10 NT servers you save to!
3) When turning off logging on the server there is a much lower risk of the servers crashing (espacially true when it comes to NT! - hehe)
4) I get a lot more usefull information then what I do with server minitors. E.g.:
- Stop Request (each time a user hit the STOP botton I can see that - you can't with server logging)
- The users REAL connection speed to the server (I can even serve different content or pages depending on that connection speed - in real time!)
- True time taken - the complete time it takes for a request to be processed - not just the time it takes for the server (as it is with server loggin).
And I could keep on ... hehehe
There is just no reason what so ever for me to stay with server logging :)