We chose awstats on three criteria apperance, speed and size of crunch down file.
We run this as a cron job on all our sites currently and have found even with DNS lookup on its acceptable.
The crunch file we have found to be of an acceptable size. But the main reason for choosing awstats is the look and feel of the reports. They are the closest to Webtrends i've seen in the opensource world. IMHO if the end user can't understand the stats quickly they are useless.
We are looking to go to an real-time model in the future, but that will need more testing. We have what I would call a high traffic site coming on stream in the next month, I'll have more info then.
I hope this helps
Tony
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
The question I asked was the simplest regarding Webalizer. My problem is that all pages are summated into one (/ aka index.php).
I would think a CMS like eZp so sofisticated would have a need for more aqurate stats than what Webalizer offers (or seems to offer).
Why good people are you recommending Webalizer?
Just to clearify... I have used Analog (and other heavy packages) since the dawn of time so I am very familiar with quite complex stats-tools :-) I just wanted to test what the eZ's recommended.
I was also wondering, why do ezcrew always recommend webalizer ?
I have used webalizer and phpopentracker, while I think that webalizer could be easier to install and keep up2date, I prefer phpopentracker output, and logs stored into db
Is there anyone using phpopentracker or something alike ?
Testing Webalizer using webalizer-2.01-10-win32-bin.zip
As far as I can figure out the "feature" Webalizer has that counts /index.* as / is hardcoded in the Webalizer-source (since they usually produce the same output on many sites).
I found an article addressing this issue on http://ertw.com/blog/archives/2003_12.html which points at the code-line involved; add_nlist("index.",&index_alias);
A solution may be to recompile Webalizer without this code-line (maybe somebody already have done it ?).
One "workaround" just to test Webaliser on an eZ site with site access configuration that show index.php is to copy the access-logfile, doing a "search and replace" to replace occurences of "/index.php/" with "/" and then let Webalizer analyze it. This gives more detailed information on which URL's has been visited in the eZ-site.
Olav..
You must be logged in to post messages in this topic!
