awstats vs analog

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

1. I wanted to know how come awstats and analog stats show different
stats, like number of unique visitors, page views and stuff... i guess
they process the raw log files differently but which is accurate, which
should i look at? analog shows me almost twice more visitors than

2. Can i completely ignore all stats from bots like google bots... i
dont want the stats to store anything about bots... i only want to see
everything that is going on the website by humans... page views,
visitors... and so on.

thanks for your help.

Re: awstats vs analog

On 3 Dec 2006 11:40:38 -0800, Ken1 put finger to keyboard and typed:

Quoted text here. Click to load it

You can't get an accurate precise figure for visitors, because that
information isn't available to the web server. Stats packages can give
an approximation, but it's as much dependent on the definition of
"visit" as it is on the algorithm used to generate the figure. If
analog is giving you a higher value, then it's probaby using a looser
definition than awstats. But that doesn't make either of them more
accurate, it all depends on what you want to actually measure.

Quoted text here. Click to load it

Yes, that's possible, at least within reasonable limits. Read the
documentation for your stats packages and configure them accordingly.
However, you do need to be aware that the User-Agent string is only a
text field set by the user; a lot of bots will pretend to be
human-driven browsers and a not-insignificant number of humans
configure their browsers to look like bots. You won't ever be able to
tell for certain which is which.

Please give me one!
"Emotions run deep as oceans"

Re: awstats vs analog

Ken1 wrote:
Quoted text here. Click to load it

You can also just skip logging for specific requests by modifying the
.htaccess file in Apache, if that's what you want to do.

Conditional Logs

There are times when it is convenient to exclude certain entries from
the access logs based on characteristics of the client request. This is
easily accomplished with the help of environment variables. First, an
environment variable must be set to indicate that the request meets
certain conditions. This is usually accomplished with SetEnvIf. Then
the env= clause of the CustomLog directive is used to include or
exclude requests where the environment variable is set. Some examples:

# Mark requests from the loop-back interface
SetEnvIf Remote_Addr "127\.0\.0\.1" dontlog
# Mark requests for the robots.txt file
SetEnvIf Request_URI "^/robots\.txt$" dontlog
# Log what remains
CustomLog logs/access_log common env=!dontlog

Re: awstats vs analog

Ken1 wrote

Quoted text here. Click to load it

You might be interested in this:

Charles Sweeney

Site Timeline