From: eldy <>
Date: Sun, 1 May 2005 17:42:40 +0000 (+0000)
Subject: Review of AWStats documentation
X-Git-Tag: AWSTATS_WEBMIN_1_6_BETA~37
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ae3e54350748040caa2d2cb15d07ea6fd03ba0a4;p=thirdparty%2FAWStats.git
Review of AWStats documentation
---
diff --git a/docs/awstats_faq.html b/docs/awstats_faq.html
index 1e3c500e..5ca8528b 100644
--- a/docs/awstats_faq.html
+++ b/docs/awstats_faq.html
@@ -229,8 +229,13 @@ However your system (Operating System or Perl version) might have a limit. For e
experience size limit errors on files larger than 2 or 4 GB.
If limit is Perl only, try to use a Perl version compiled with "large file" option.
If you can't find it nor build it, you can try to use a LogFile parameter that looks like this
-LogFile="cat /yourlogfilepath/yourlogfile |" instead of
-LogFile="/yourlogfilepath/yourlogfile"
+
+LogFile="cat /yourlogfilepath/yourlogfile |"
+
+instead of
+
+LogFile="/yourlogfilepath/yourlogfile"
+
@@ -262,7 +267,9 @@ Then turn off old format Transfer log:
To have the change effective, stop your server, remove old log file /var/log/xferlog and restart the server.
Download a file by FTP and check that your new log file looks like this:
+
[01/Jan/2001:21:49:57 +0200] ftp.server.com user RETR /home/fileiget.txt 226 1499
+
2- Then setup AWStats to analyze the FTP log file:
@@ -505,9 +512,11 @@ What do I have to do to use AWStats to analyze my Media Server log files. For Realmedia
Copy config awstats.model.conf file to "awstats.mediaserver.conf".
Modify this new config file:
@@ -550,8 +559,9 @@ Now you can use AWStats as usual (run the update process and read statistics).For Windows Media Server / Darwin Streaming Server
1- If your Windows Media / Darwin streaming Server version allows it, setup your log format to write the following fields:
+
- c-ip
+c-ip
date
time
cs-uri-stem
@@ -579,18 +589,22 @@ Now you can use AWStats as usual (run the update process and read statistics).channelURL
sc-bytes
+
To have the change effective, stop your server, remove old log files and restart the server.
Listen to streaming files and check that your new log file looks like this:
+
If your Windows Media/Darwin Streaming Server version does not allow to define your log format:
Just follow instructions in step 2 directly but use the log format string found in first lines
of your log files (Just after the "#Fields:" string) as value for AWStats LogFormat
parameter. For example, you could have a LogFormat defined like this:
+
This means you don't use the AWStats tags but AWStats can often also understand all the IIS and/or
Windows Media Server tags.
@@ -654,32 +669,29 @@ The AWStats config file give you all possible values for LogFormat parameter.
To help you, this is some common cases of log file format, and
the corresponding value for LogFormat you must use in your AWStats config file:
-
If your log records are EXACTLY like this (NCSA combined/XLF/ELF log format): 62.161.78.73 - - [dd/mmm/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" 200 1234 "http://www.from.com/from.htm" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
You must use : LogFormat=1
This is same than: LogFormat="%host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot"
-
+
If your log records are EXACTLY like this (NCSA combined with several virtualhostname sharing same log file). virtualserver1 62.161.78.73 - - [dd/mmm/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" 200 1234 "http://www.from.com/from.htm" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
You must use : LogFormat="%virtualname %host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot"
-
If your log records are EXACTLY like this (NCSA combined and mod_gzip format 1 with Apache 1.x): 62.161.78.73 - - [dd/mmm/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" 200 3904 "http://www.from.com/from.htm" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)" mod_gzip: 66pct.
You must use : LogFormat="%host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot %other %gzipratio"
-
+
If your log records are EXACTLY like this (NCSA combined and mod_gzip format 2 with Apache 1.x): 62.161.78.73 - - [dd/mmm/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" 200 3904 "http://www.from.com/from.htm" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)" mod_gzip: DECHUNK:OK In:11393 Out:3904:66pct.
You must use : LogFormat="%host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot %other %other %gzipin %gzipout"
-
If your log records are EXACTLY like this (NCSA combined and mod_deflate with Apache 2): 62.161.78.73 - - [dd/mmm/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" 200 3904 "http://www.from.com/from.htm" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)" (45)
You must use : LogFormat="%host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot %deflateratio"
-
+
If your log records are EXACTLY like this (NCSA combined with 2 spaces between some fields with Zope): 62.161.78.73 - - [dd/mmm/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" 200 3904 "http://www.from.com/from.htm" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)" (45)
@@ -688,32 +700,29 @@ LogFormat="%host %other %logname %time1 %methodurl %code %bytesd %refererquot %u
LogSeparator=" *"
-
If your log records are EXACTLY like this (NCSA common CLF log format): 62.161.78.73 - - [dd/mmm/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" 200 1234
You must use : LogFormat=4
Note: Browsers, OS's, Keywords and Referers features are not available with a such format.
-
+
If your log records are EXACTLY like this (With some Squid versions, after setting emulate_http_log to on): 200.135.30.181 - - [dd/mmm/yyyy:hh:mm:ss +0x00] "GET http://www.mydomain.com/page.html HTTP/1.0" 200 456 TCP_CLIENT_REFRESH_MISS:DIRECT
You must use : LogFormat="%host %other %logname %time1 %methodurl %code %bytesd %other"
-
If your log records are EXACTLY like this (Some old IIS W3C log format): yyyy-mm-dd hh:mm:ss 62.161.78.73 - GET /page.html 200 1234 HTTP/1.1 Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0) http://www.from.com/from.html
You must use : LogFormat=2
-
+
If your log records are EXACTLY like this (Some IIS W3C log format with some .net servers): yyyy-mm-dd hh:mm:ss GET /page.html - 62.161.78.73 - Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0) http://www.from.com/from.html 200 1234 HTTP/1.1
You must use : LogFormat=2 (or LogFormat="%time2 %method %url %logname %host %other %ua %referer %code %bytesd %other")
-
If your log records are EXACTLY like this (Some IIS 6+ W3C log format): yyyy-mm-dd hh:mm:ss GET /page.html - 62.161.78.73 - Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0) http://www.from.com/from.html 200 1234
You must use : LogFormat=2 (or LogFormat="date time cs-method cs-uri-stem cs-username c-ip cs-version cs(User-Agent) cs(Referer) sc-status sc-bytes")
-
+
If your log records are EXACTLY like this (Some ISA W3C log format): 62.161.78.73, anonymous, Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1), N, 1/1/2001, 0:00:16, W3ReverseProxy, HCSERV2, -, www.host.be, 192.168.141.101, 80, 266, 406, 10042, http, TCP, GET, http://192.168.141.101/, text/html, Inet, 200, 0x42330010, -, -
@@ -722,56 +731,51 @@ You must use : LogFormat=2 LogSeparator=" "
-
If your log records are EXACTLY like this (With some WebSite versions): yyyy-mm-dd hh:mm:ss 62.161.78.73 - 192.168.1.1 80 GET /page.html - 200 11205 0 0 HTTP/1.1 mydomain.com Mozilla/4.0+(compatible;+MSIE+5.5;+Windows+98) - http://www.from.com/from.html
You must use : LogFormat="%time2 %host %logname %other %other %method %url %other %code %bytesd %other %other %other %other %ua %other %referer"
-
+
If your log records are EXACTLY like this (Webstar native log format): 05/21/00 00:17:31 OK 200 212.242.30.6 Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt) http://www.cover.dk/ "www.cover.dk" :Documentation:graphics:starninelogo.white.gif 1133
You must use : LogFormat=3
-
If your log records are EXACTLY like this (With some Lotus Notes/Domino versions): 62.161.78.73 - Name Surname Service [dd/mmm/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" 200 1234 "http://www.from.com/from.htm" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
You must use : LogFormat=6
-
+
If your log records are EXACTLY like this (Lotus Notes/Domino 6.x log format): 62.161.78.73 - "Name Surname" Service [dd/mmm/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" 200 1234 "http://www.from.com/from.htm" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
You must use : LogFormat="%host %other %lognamequot %time1 %methodurl %code %bytesd %refererquot %uaquot"
-
If your log records are EXACTLY like this (With Oracle9iAS): 62.161.78.73 - [dd/mmm/yyyy:hh:mm:ss +0x00] GET /page.html HTTP/1.1 200 1234 - "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
Where separators are chars or several spaces,
You must use : LogFormat="%host %logname %time1 %method %url %other %code %bytesd %referer %uaquot"
and LogSeparator="\s+"
-
+
If you use a FTP server like ProFTPd:
See FAQ-COM090.
-
If you want to analyze a mail log file (Postfix, Sendmail, QMail, MDaemon, Exchange):
See FAQ-COM100.
-
+
If you use a Media Server (Realmedia, Windows Media Server):
See FAQ-COM110.
-
If your log records are EXACTLY like this (With some providers): 62.161.78.73 - - [dd/Month/yyyy:hh:mm:ss +0x00] "GET /page.html HTTP/1.1" "-" 200 1234
You must use : LogFormat="%host %other %logname %time1 %methodurl %other %code %bytesd"
Note: Browsers, OS's, Keywords and Referers features are not available with a such format.
-
+
There is a lot of other possible log formats.
You must use a personalized log format LogFormat ="..." as described in config file to
support other various log formats.
-
+
FAQ-COM120 : HOW TO ROTATE MY LOGS WITHOUT LOOSING DATA
@@ -889,19 +893,23 @@ But you can also run AWStats update process regularly by a scheduler:
The use of this tool is not an AWStats related problem, so please take a look at your Windows manual.
Warning, if you use "awstats.pl -config=mysite -update" in your scheduled task, you might
experience problem of failing task. Try this instead
-"C:\WINNT\system32\CMD.EXE /C C:\[awstats_path]\awstats.pl -config=mysite -update"
+
A lot of other open source schedulers are often better (otherwise there is also good sharewares or freewares).
With unix-like operating systems, you can use the "crontab".
This is examples of lines you can add in the cron file (see your unix reference manual for cron) :
To run update every day at 03:50, use :
-
@@ -931,7 +939,7 @@ get screen size use ratios). This tag will add call to a javascript that ask you
includes in its parameters, the screen size resolution and other informations about browser capabilities.
This is the code you must add (at bottom of your home page for example) :
-
@@ -940,14 +948,14 @@ Note that you must also place the awstats_misc_tracker.js script (provide
a js directory stored in your web root.
Once this is done, load your home page with your browser and go to check that inside your log file
if you can see a line that looks like that:
-
If yes, you can then run the AWStats update process. Screen sizes information will be analyzed. All you have to do
now is to edit your config file to tell AWStats to add the report on html output. For this, change
the ShowMiscStats parameter.
-
+
ShowMiscStats=anjdfrqwp
@@ -1177,7 +1185,7 @@ is by design.
So this means this way of working might never be changed, so another chance is to use the AWStats plugin 'timezone'.
Warning, this plugin need the perl module Time::Local and it reduces seriously AWStats speed.
To enable the plugin, uncomment the following line in your config file.
-
+
LoadPlugin="timezone TZ"
where TZ is value of your signed timezone (+2 for Paris, -8 for ...)
@@ -1220,7 +1228,7 @@ A solution should be to setup your config file with something like: LogFile=mylog*.log
However, with such a syntax, AWStats can't know in wich order processing log files (wich log file is the first, next or last). So
to work like this you must use the following syntax:
-
+
LogFile="/pathto/logresolvemerge.pl mylog*.log |"
Logresolvemerge is a tool provided with
@@ -1244,7 +1252,7 @@ And setup the LogFile parameter in you
the -LogFile command line option to overwrite LogFile value.
As an other solution, if you miss disk space, or to save time, you can ask logresolvemerge
to merge log files on the fly during the AWStats update process. For this, you can use the following syntax in your AWStats config file:
-
+
LogFile="/pathto/logresolvemerge.pl file*.log |"
See also FAQ-COM360 for explanation on logresolvemerge use.
@@ -1349,7 +1357,7 @@ servers with no internal Perl interpreter (mod_perl not active). To solve this,
tell Apache where is your external Perl interpreter. For this, you have 2 solutions:
1) Add the following directive in your Apache httpd.conf config (or remove the # to uncomment it if line is already available)
-
+
ScriptInterpreterSource registry
Then restart Apache. This will tell Apache to look into the registry to find the program associated to .pl extension.
@@ -1567,8 +1575,10 @@ where YYYY and MM are year and month of config file and 999 are numerical values
So if your OS is Unix/Linux
+
And then run the migrate process again on the file.
@@ -1650,7 +1660,7 @@ However, this feature reduce seriously AWStats speed and the worms database (lib
all worms signatures. So if you still have rubish hits, you can modify the worms.pm file yourself or
edit your config file to add in the SkipFiles parameter some
values to discard the not required records, using a regex syntax like example :
-
@@ -46,320 +52,530 @@ AWStats common use is made in 3 phases:
Before starting, check that your Perl version is at least 5.005_03 (or higher) by running the perl -v command.
If not, you can install a recent Perl interpreter from ActivePerl (Win32) or Perl.com (Unix/Linux/Other).
-->
-
-* Step 1:
-
-(if you use a package provided with a Linux distribution or Windows installer, action done in step 1
-might have already be done, if you don't know, you can run this step again)
-
-After downloading and extracting the AWStats package, you should run the awstats_configure.pl script to do
+
+
+
+A) Setup for an Apache or compatible web
+server (on Unix/Linux, Windows, MacOS...)
+
+* Step 1:
+
+(if you use a package provided with a Linux distribution or Windows
+installer, step 1
+might have already been done; if you don't know, you can run this step
+again)
+
+After downloading and extracting the AWStats package, you should run
+the awstats_configure.pl script to do
several setup actions.
-You will find it in the AWStats tools directory (If using the Windows installer, the script is
+You will find it in the AWStats tools directory (If using the
+Windows installer, the script is
automatically launched):
-perl awstats_configure.pl
-
+
+perl awstats_configure.pl
+
+
-
-This is what the script do/ask (you can do all those steps manually instead of running awstats_configure.pl if you prefer):
+ This is what the script does/asks (you can do all these steps
+manually instead of running awstats_configure.pl if you prefer):
-
-A) awstats_configure.pl try to find your Apache web server config file (ask path if not found) and check
-inside your server log format configuration.
+A) awstats_configure.pl tries to determine your current log format from
+your Apache web server
+configuration file httpd.conf (it asks for the path if not found).
If you use a common log, awstats_configure.pl will
-suggest to change it to have NCSA combined/XLF/ELF log format (you can use your own log
-format but this predefined logformat is often the best choice and make setup easier).
-If you answer yes, awstats_configure.pl will modify your httpd.conf to change all the
-following directives:
-CustomLog /yourlogpath/yourlogfile common
-into
+suggest changing it to the NCSA combined/XLF/ELF format (you
+can use your own custom log
+format but this predefined log format is often the best choice and
+makes setup easier).
+If you answer yes, awstats_configure.pl will modify your httpd.conf,
+changing the
+following directive:
+ from
+CustomLog /yourlogpath/yourlogfile common
+to CustomLog /yourlogpath/yourlogfile combined
-See your Apache manual for more information on this directive.
-To be sure the log format change is effective, later you can stop Apache, remove all old
-log files, restart Apache and go to your homepage. This is an example of records you
-should get then in your new log file:
-62.161.78.75 - - [dd/mmm/yyyy:hh:mm:ss +0000] "GET / HTTP/1.1" 200 1234 "http://www.from.com/from.html" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
-
-
-B) Then, awstats_configure.pl will add, if not already present, the following directives to your Apache config file
-(note that the "/usr/local/awstats/wwwroot" path might differ according to your distribution or OS:
-
- #
- # Directives to add to your Apache conf file to allow use of AWStats as a CGI.
- # Note that path "/usr/local/awstats/" must reflect your AWStats install path.
- #
- Alias /awstatsclasses "/usr/local/awstats/wwwroot/classes/"
- Alias /awstatscss "/usr/local/awstats/wwwroot/css/"
- Alias /awstatsicons "/usr/local/awstats/wwwroot/icon/"
- ScriptAlias /awstats/ "/usr/local/awstats/wwwroot/cgi-bin/"
- #
- # This is to permit URL access to scripts/files in AWStats directory.
- #
- <Directory "/usr/local/awstats/wwwroot">
- Options None
- AllowOverride None
- Order allow,deny
- Allow from all
- </Directory>
-
-
-
-
-C) awstats_configure.pl restart Apache to apply the changes made in A and B (if changes were made).
-
-
-D) awstats_configure.pl will ask you a name for a config profile file. Enter here the name of your
-web server or any analysis profile name, for example myvirtualhostname.
-So awstats_configure.pl will copy the file awstats.model.conf file into a new file
-named awstats.myvirtualhostname.conf.
-You can use the value of your choice instead of "myvirtualhostname". This new file is stored into:
+See the Apache manual for more information on this directive (possibly
+installed on your server as www.mysite.com/manual).
+
+B) awstats_configure.pl will then add, if not already present, the
+following directives to your Apache configuration file
+(note that the "/usr/local/awstats/wwwroot" path might differ according
+to your distribution or OS:
+
+#
+# Directives to add to your Apache conf file to allow use of AWStats as
+a CGI.
+# Note that path "/usr/local/awstats/" must reflect your AWStats
+Installation path.
+#
+Alias /awstatsclasses "/usr/local/awstats/wwwroot/classes/"
+Alias /awstatscss "/usr/local/awstats/wwwroot/css/"
+Alias /awstatsicons "/usr/local/awstats/wwwroot/icon/"
+ScriptAlias /awstats/ "/usr/local/awstats/wwwroot/cgi-bin/"
+#
+# This is to permit URL access to scripts/files in AWStats directory.
+#
+<Directory "/usr/local/awstats/wwwroot">
+Options None
+AllowOverride None
+Order allow,deny
+Allow from all
+</Directory>
+
+C) if changes were made as indicated in parts A and B,
+awstats_configure.pl restarts Apache to apply the changes. To be
+sure the log format change is effective, go to your homepage. This is
+an example of the type of records you should see inserted in your new
+log file after Apache
+was restarted:
+
+62.161.78.75 - - [dd/mmm/yyyy:hh:mm:ss +0000] "GET / HTTP/1.1" 200 1234
+"http://www.from.com/from.html" "Mozilla/4.0 (compatible; MSIE 5.01;
+Windows NT 5.0)"
+
+D) awstats_configure.pl will ask you for a name for the configuration
+profile file. Enter an appropriate name such as that of your
+web server or the virtual domain to be analyzed, i.e. mysite.
+
+awstats_configure.pl will create a new file called awstats.mysite.conf
+by copying the template file awstats.model.conf.
+The new file location is:
- For Linux/BSD/Unix users: /etc/awstats.
-- For Mac OS X, Windows and other OS: Same directory than awstats.pl (so cgi-bin).
+- For Mac OS X, Windows and other operating systems: the same directory
+as awstats.pl
+(cgi-bin).
E) awstats_configure.pl ends.
-
-* Step 2:
-
-Once a config file has been automatically created (by awstats_configure.pl, by your package
-installer or just by a manual copy of awstats.model.conf), it's important to edit it manually and change the "MAIN PARAMETERS"
-to match all your needs:
-
-This is for example the parameters you should check seriously :
-- Check/Change LogFile value with full path of your server log file (You
-can also use a relative path from your awstats.pl directory, but full path avoid errors).
-- Check/Change LogType value with "W" for analyzing
-web server log files, "S" for a streaming server log file, "M" for mail log files, "F" for ftp log files.
-- Check if LogFormat has the value "1" (it means "NCSA apache combined/ELF/XLF log format")
-or use a personalized log format if you don't use combined log format.
-- Edit SiteDomain parameter with the main domain name or the intranet
-web server name used to reach the web site to analyze (Example: www.mydomain.com). If you have several
-possible name for same site, use the main domain name and add list of others in HostAlias parameter.
-- You can also change other parameters if you want. Full list is available in Configurations/Directives options page.
-
-
-Install and Setup is finished. You can jump to the Building/Updating statistics database section.
-
-
-
-
-
-B) Setup with IIS server
-
-* Step 1:
-
-Configure IIS to log in "Extended W3C log format" (You can still use
-your own log format but setup is easier if made like suggested). So, for
-this, start the IIS Snap-in, select the web site and look at its
-Properties. Choose W3C Extended Log Format, then Properties, then the
-Tab Extended Properties and uncheck everything under Extended Properties.
-Once they are all unchecked, check all following fields:
-
-date
-time
-c-ip
-cs-username
-cs-method
-cs-uri-stem
-cs-uri-query
-sc-status
-sc-bytes
-cs-version
-cs(User-Agent)
-cs(Referer)
-
-To be sure the log format change is effective, you must stop IIS, remove all old log files, restart IIS and go to
-your homepage. This is an example of records you should get then in the new log file:
-2000-07-19 14:14:14 62.161.78.73 - GET / 200 1234 HTTP/1.1 Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0) http://www.from.com/from.htm
+* Step 2:
+
+Once a configuration file has been created (by
+awstats_configure.pl, by your package
+installer or just by a manual copy of awstats.model.conf), it's
+important to verify that the "MAIN PARAMETERS"
+match your needs. Open awstats.mysite.conf in
+your favorite text editor (i.e. notepad.exe, vi, gedit, etc) -
+don´t use a word processor - and make changes as required.
+
+Particular attention should be given to these parameters:
+- Verify the LogFile
+value. It should be the full path of your server log file (You
+can also use a relative path from your awstats.pl directory, but a full
+path avoids errors).
+- Verify the LogType
+value. It should be "W" for analyzing
+web log files.
+- Check if LogFormat is
+set to "1" (for "NCSA apache combined/ELF/XLF log format")
+or use a custom log format if you don't use the combined log format.
+- Set the SiteDomain
+parameter to the main domain name or the intranet web server name
+used to reach the web site to analyze (Example: www.mysite.com). If
+you have several
+possible names for same site, use the main domain name and add the
+others to the list in the HostAlias
+parameter.
+- You can also change other parameters if you want. The full list is
+described in Configurations/Directives
+options page.
+
+Installation and configuration is finished. You can jump to the Process logs: Building/updating statistics
+database section.
-
-* Step 2:
-
-Copy the contents of the provided cgi-bin folder from your hard drive to your server's cgi-bin
-directory (this includes awstats.pl, awstats.model.conf, and the lang, lib and plugins sub-directories).
-
-* Step 3:
-Move AWStats icon sub-directories and its content into a directory readable by your
-web server, for example C:\yourwwwroot\icon.
-
-
-* Step 4:
-
-Create a config file by copying awstats.model.conf file into a new file named awstats.myvirtualhostname.conf.
-You can use the value of your choice instead of "myvirtualhostname". This new file must be stored in
-- Same directory than awstats.pl (so cgi-bin)
-
-
-* Step 5:
-
-Edit this new config file with your own setup :
-- Change LogFile value with full path of your web server log file (You
-can also use a relative path from your awstats.pl directory).
-- Change LogType value with "W" for analyzing
-web server log files, "S" for a streaming server log file, "M" for mail log files, "F" for ftp log files, "O" otherwise.
-- Change LogFormat to a value with same field's name defined in step 1:
-LogFormat="date time c-ip cs-username cs-method cs-uri-stem cs-uri-query sc-status sc-bytes cs-version cs(User-Agent) cs(Referer)"
-- Change DirIcons parameter to reflect relative path of icon directory.
-- Edit SiteDomain parameter with the main domain name or the intranet
-web server name used to reach the web site to analyze (Example: www.mydomain.com).
-- Set AllowToUpdateStatsFromBrowser parameter to 1 if you don't have command line access and have only cgi access.
-- You can change other parameters if you want.
-
-Install and Setup is finished. You can jump to the Building/Updating statistics database section.
-
-
-
-
-C) Setup with other web servers
-
-Setup process is similar to setup for Apache or IIS.
-Use LogFormat to value "3" if you have WebStar native log format, use
-a personalized LogFormat if your log format is other.
-
-
-
-
-
-
-
-
-* Step 1:
-
-The first analyze/update of statistics should be made the first time manually from the command line since first time,
-process may be long and it's easier to solve problems (if you don't have Command Line access, just go to Step 2). The
-AWStats update command line is:
-awstats.pl -config=myvirtualhostname -update
-
-AWStats will read the config file awstats.myvirtualhostname.conf (or if not found, awstats.conf)
-and create/update its database with all summary information issued from analyzed log file.
-AWStats database files are saved in directory defined in config file by DirData parameter.
-When update is finished, you should get on screen a result like this:
-
-Update for config "/etc/awstats/awstats.myvirtualhostname.conf"
+B) Setup for Microsoft's IIS server
+
+* Step 1:
+
+Configure IIS to log in the "Extended W3C log format" (You can
+still use
+your own custom log format but setup is easier if you use the standard
+extended format). To do so, start the IIS management console snap-in,
+select the
+appropriate web site and open its
+Properties. Choose "W3C Extended Log Format", then Properties, then the
+Tab "Extended Properties" and
+uncheck everything under Extended
+Properties.
+Once they are all cleared, check just the following fields:
+
+
+To be sure the log format change is effective, you must stop IIS,
+backup (if desired) and remove all old log files, restart IIS and go to
+your homepage. This is an example of the type of records you should
+find in the
+new log file:
+
+
+
+* Step 2:
+
+Copy the contents of the AWStats provided cgi-bin folder from where
+your AWStats package put it on your local hard
+drive
+to your server's cgi-bin
+directory (this includes awstats.pl, awstats.model.conf,
+and the lang, lib and plugins sub-directories).
+
+* Step 3:
+
+Move AWStats icon sub-directories and its content into a
+directory readable by your
+web server, for example C:\yourwwwroot\icon.
+
+* Step 4:
+
+Create a configuration file by copying awstats.model.conf to a
+new file named awstats.mysite.conf
+where "mysite" is a
+value of your choice but usually is the domain or virtual host name.
+This new file must be saved in the same directory as awstats.pl (i.e.
+cgi-bin).
+
+* Step 5:
+
+Edit your new awstats.mysite.conf
+file to match your specific environment:
+- Change the LogFile value
+to the
+full path of your web server log file (You
+can also use a relative path from your awstats.pl (cgi-bin) directory).
+- Change the LogType value
+to
+"W" for analyzing
+web log files.
+- Change the LogFormat to
+2 if you are using the "Extended W3C log format" described in
+step 1; in the case of a custom format, list the IIS fields
+being logged, for example:
+LogFormat="date time c-ip cs-username cs-method cs-uri-stem
+cs-uri-query sc-status sc-bytes cs-version cs(User-Agent) cs(Referer)"
+- Change the DirIcons
+parameter
+to reflect relative path of icon directory.
+- Set the SiteDomain
+parameter to the main domain name or the intranet
+web server name used to reach the web site being analyzed (Example:
+www.mydomain.com).
+- Set the AllowToUpdateStatsFromBrowser
+parameter to 1 if you don't have command line access and have only cgi
+access.
+- Review and change other parameters if appropriate.
+
+Installation and configuration is finished. You can jump to the Process logs: Building/Updating statistics
+database section.
+
+C) Setup for other web servers
+
+The setup process is similar to the setup for Apache or IIS.
+Use LogFormat to value "3"
+if you have WebStar native log format, use
+a personalized LogFormat
+if your log format is other.
+
+D) Setup for other Internet servers, i.e. FTP, Mail, Streaming media
+
+The setup process for other file formats is described in the relevant
+FAQ topics:
+FAQ-COM090: FTP
+FAQ-COM100: Mail and FAQ-COM110: Streaming media.
+
+
+
+
+
+
+* Update from command line (recommanded):
+
+The first log analysis should be done
+manually from the command line since the
+process may be long and it's easier to solve problems when you can see
+the
+command output (if you don't
+have Command Line access, skip to Step 2). The
+AWStats create (and update) statistics database command is:
+
+
+perl awstats.pl -config=mysite -update
+
+
+where mysite must
+be substituted with the domain/virtual host name you selected earlier
+during AWStats configuration.
+
+AWStats will read the configuration file awstats.mysite.conf
+(or if
+not found, awstats.conf)
+and create/update its database with all summary information issued from
+analyzed log file.
+
+AWStats statistics database files are saved in directory defined by the
+DirData parameter in
+configuration file.
+When the create/update is finished, you should see a similar result on
+your screen:
+
+
+Update for config "/etc/awstats/awstats.mysite.conf"
With data in log file "/pathtoyourlog/yourlog.log"...
Phase 1 : First bypass old records, searching new record...
Searching new records from beginning of log file...
-Phase 2 : Now process new records (Flush history on disk after 20000 hosts)...
+Phase 2 : Now process new records (Flush history on disk after 20000
+hosts)...
Jumped lines in file: 0
Parsed lines in file: 225730
Found 122 dropped records,
Found 87 corrupted records,
Found 0 old records,
- Found 225521 new qualifed records.
-
-Dropped records are records discarded because they were not "user HTTP requests" or requests were not qualified
-by AWStats filters (See SkipHosts, SkipUserAgents,
-SkipFiles, OnlyHosts,
-OnlyUserAgents and OnlyFiles parameters).
-If you want to see which lines were dropped, you can add the -showdropped option on command line.
-Corrupted records are records that does not match log format defined by "LogFormat" parameter in AWStats config/domain file.
-With all webservers you can experience a little bit corrupted records (<5%) even when everythings work correctly.
-This can be the result of several reasons: Web server internal bugs, bad requests made by buggy browsers, web server brutal stop...
-If all your lines are corrupted and LogFormat parameter in AWStats config/domain file is
-correct, it may be the log format setup in your web server that is wrong. Don't forget that
-your LogFormat parameter in AWStats config/domain file MUST match
-the log file format you analyze.
-If you want to see which lines are corrupted, you can add the -showcorrupted option on command line.
-Old records are simply records that were already processed by a previous update process.
-You understood that it's not necessary to purge your log file after each update process even
-if it's highly recommended to do it as often as possible.
-New records are records in your log file that were successfully used to build/update statistics.
-
-Note : A log analysis process might be slow (one second for each 4500 lines of your
-logfile with Athlon 1Ghz, plus DNS resolution time for each different IP
-address in your logfile if DNSLookup is set to 1 and not already done in your log file).
-See Benchmark page for more accurate information.
-
-
-* Step 2:
-
-AWStats statistics can also be updated from a browser, to provide real-time statistics, by clicking
-the "Update now" link that appears when AWStats is used as a CGI (Next section 'Reports build: Building and reading reports
-dynamically' gives you URL to use for that).
+ Found 225521 new qualified records.
+
+
+Dropped records are records discarded because they were not
+"user HTTP requests" or were requests matching AWStats filters (See the
+SkipHosts,
+SkipUserAgents,
+SkipFiles, OnlyHosts,
+OnlyUserAgents and OnlyFiles parameters).
+If you want to see which lines were dropped, you can add the -showdropped
+option on the command line.
+
+Corrupted records are records that does not match log format
+defined by "LogFormat" parameter in AWStats configuration file.
+All web servers will typically have a few corrupted records
+(<5%) even when everything works correctly.
+This can result for several reasons: 1) Web server internal bugs,
+2) bad requests made by buggy browsers, 3) a dirty web server shutdown,
+such as unplugging the server...
+
+If all your lines are corrupted and the LogFormat parameter in
+AWStats configuration file is
+correct, there may be a setup problem with your web server log format.
+Don't forget that
+your LogFormat parameter
+in the AWStats configuration file MUST match
+the log file format you analyze. If you want to see which lines
+are corrupted, you can add the -showcorrupted
+option on the command line.
+
+Old records are simply records that were already processed by a
+previous update session.
+Although it is not necessary to purge your log file after
+each update process, it is highly recommended that you do so as often
+as possible.
+
+New records are records in your log file that were successfully
+used to build/update the statistics database.
+
+Note: A log analysis process might be slow (one second for each 4500
+lines of your
+logfile with an Athlon 1Ghz, plus DNS resolution time for each
+different
+IP
+address in your logfile if DNSLookup
+is set to 1 and not already done in your log file). See the Benchmarks page for more detailed
+information.
+
+
+
+
+* Update from a browser:
+
+AWStats statistics can also be updated from a browser, providing
+real-time statistics, by clicking
+the "Update now" link that appears when AWStats is used as a CGI (The
+URL is described in the next
+section 'Run reports: Building and reading reports').
Warning!!
-To enable this link, your parameter AllowToUpdateStatsFromBrowser
-must be set to 1 in your config file (Link is not enabled by default).
-Then, using on-line update does not prevent you from running the update process from a scheduler
-frequently (command is same than update of first update process).
+To enable this link, the configuration file parameter AllowToUpdateStatsFromBrowser
+must be set to 1 (The link is not enabled by
+default).
+Using the on-line update does not prevent you from running the update
+process automatically on a scheduled basis (the command is same as that
+of the first update process above).
For this, you have two choices:
-- Include the update command in your logrotate process. See FAQ-COM120 for this.
-- Or add instructions in your crontab (Unix/Linux) or your task scheduler (for
-Windows), to launch frequently the Awstats update process. See FAQ-COM130 for this.
-
-
-To see results of analyze, you have several solutions depending on your security policy.
-
-
-* First solution is to build the main reports, in a static HTML page, from the command line,
-like this (jump to second solution if you have ONLY CGI access):
-perl awstats.pl -config=myvirtualhostname -output -staticlinks > awstats.myvirtualhostname.html
-
-You can use all other output options (each of them give you another report).
-This is how to use all other possible output options(1) :
-perl awstats.pl -config=myvirtualhostname -output=alldomains -staticlinks > awstats.myvirtualhostname.alldomains.html
-perl awstats.pl -config=myvirtualhostname -output=allhosts -staticlinks > awstats.myvirtualhostname.allhosts.html
-perl awstats.pl -config=myvirtualhostname -output=lasthosts -staticlinks > awstats.myvirtualhostname.lasthosts.html
-perl awstats.pl -config=myvirtualhostname -output=unknownip -staticlinks > awstats.myvirtualhostname.unknownip.html
-perl awstats.pl -config=myvirtualhostname -output=alllogins -staticlinks > awstats.myvirtualhostname.alllogins.html
-perl awstats.pl -config=myvirtualhostname -output=lastlogins -staticlinks > awstats.myvirtualhostname.lastlogins.html
-perl awstats.pl -config=myvirtualhostname -output=allrobots -staticlinks > awstats.myvirtualhostname.allrobots.html
-perl awstats.pl -config=myvirtualhostname -output=lastrobots -staticlinks > awstats.myvirtualhostname.lastrobots.html
-perl awstats.pl -config=myvirtualhostname -output=urldetail -staticlinks > awstats.myvirtualhostname.urldetail.html
-perl awstats.pl -config=myvirtualhostname -output=urlentry -staticlinks > awstats.myvirtualhostname.urlentry.html
-perl awstats.pl -config=myvirtualhostname -output=urlexit -staticlinks > awstats.myvirtualhostname.urlexit.html
-perl awstats.pl -config=myvirtualhostname -output=browserdetail -staticlinks > awstats.myvirtualhostname.browserdetail.html
-perl awstats.pl -config=myvirtualhostname -output=osdetail -staticlinks > awstats.myvirtualhostname.osdetail.html
-perl awstats.pl -config=myvirtualhostname -output=unknownbrowser -staticlinks > awstats.myvirtualhostname.unknownbrowser.html
-perl awstats.pl -config=myvirtualhostname -output=unknownos -staticlinks > awstats.myvirtualhostname.unknownos.html
-perl awstats.pl -config=myvirtualhostname -output=refererse -staticlinks > awstats.myvirtualhostname.refererse.html
-perl awstats.pl -config=myvirtualhostname -output=refererpages -staticlinks > awstats.myvirtualhostname.refererpages.html
-perl awstats.pl -config=myvirtualhostname -output=keyphrases -staticlinks > awstats.myvirtualhostname.keyphrases.html
-perl awstats.pl -config=myvirtualhostname -output=keywords -staticlinks > awstats.myvirtualhostname.keywords.html
-perl awstats.pl -config=myvirtualhostname -output=errors404 -staticlinks > awstats.myvirtualhostname.errors404.html
-
-Note (1): If you prefer, you can use awstats_buildstaticpages tool to
-build all those pages in one command, or to generate PDF files.
-
-Note (2): You can also add a filter on the following output reports:urldetail, urlentry, urlexit, allhosts, refererpages.
-filter can be a regexp on the full key you want awstats to present information about and you must use it after the output
+- Include the update command in your logrotate process. See FAQ-COM120 for details.
+- Or add instructions in your crontab (Unix/Linux) or your task
+scheduler (Windows), to regularly launch the Awstats update
+process. See FAQ-COM130 for
+details.
+
+See the AWStats Benchmarks page
+for
+the recommended update/logrotate frequency.
+
+
+
+
+
+
+To see the analysis results, you have several options depending on your
+security policy.
+
+Note: you must have created a statistics data base for the analysis
+period by processing your
+log files before you try to create reports. See the previous
+section.
+
+1. The first option is to build the main reports, in a static HTML
+page,
+from the command line,
+using the following syntax (skip to the second option if you only have
+CGI access):
+
+
+
+where mysite must
+be substituted with the domain/virtual host name you selected earlier
+during AWStats configuration.
+
+To create specific individual reports, specify the report name on the
+command
+line as follows¹:
+
+
+¹If you prefer, you can use the awstats_buildstaticpages
+tool to
+build all these pages in one command, or to generate PDF files.
+
+Notes:
+
+a) You can also add a filter on the following reports: urldetail,
+urlentry, urlexit, allhosts, refererpages. The filter
+can be a regexp (regular expression) on the full key you want AWStats
+to report on and is appended to the output
parameter separated by a ":".
-For example, to output the urldetail report, with a filter on all pages that contains /news, you
+
+For example, to output the urldetail report, including only pages which
+contain /news in their URL, you
can use the following command line:
-perl awstats.pl -config=myvirtualhostname -output=urldetail:/news -staticlinks > awstats.myvirtualhostname.urldetailwithfilter.html
+
+
+b) If you want to build a report for a particular month, add
+the options -month=MM -year=YYYY where MM is the month
+expressed as two digits, i.e. 03, and year is the four digit
+year. To build a
+report for a full year, add the options -month=all -year=YYYY
+(warning: this is often resource intensive and might use a lot of
+memory
+and CPU. Unix/Linux like operating systems might benefit from use
+of the "nice" command.)
+
+
+2) The second option is to dynamically view your statistics from a
+browser. To do this, use the URL:
+
+
+where mysite specifies the configuration
+file to
+use (AWStats will use the file awstats.mysite.conf).
+
+All output command line options (except -staticlinks) are
+also available when using AWStats with a browser. Just use them as URL
+parameters: change "-option" to
+"&option", i.e. http://www.myserver.mydomain/awstats/awstats.pl?month=MM&year=YYYY&output=unknownos
+
+Reports are generated in real time from the statistics data
+base. If this is slow, or putting too much load on your server,
+consider generating static reports instead.
+
+If the AllowToUpdateStatsFromBrowser
+parameter is set to 1 in AWStats configuration file,
+you will also be able to run the update process from your browser. Just
+click on the link "Update now".
+
-Note (3): If you want to build a report for a particular month, add options -month=MM -year=YYYY.
-To build a report for full year (warning: This may use a lot of memory and CPU), add options -month=all -year=YYYY.
-
-
-* Second solution is to view dynamically your statistics from a browser. For this, use URL:
-http://www.myserver.mydomain/awstats/awstats.pl?config=myvirtualhostname
-where myvirtualhostname is used to know which config file to use (AWStats will use awstats.myvirtualhostname.conf file).
-
-Note (1): All output command line options (except -staticlinks) are still available when using AWStats as a browser.
-Just use them as URL parameters like this example http://www.myserver.mydomain/awstats/awstats.pl?month=MM&year=YYYY&output=unknownos
-
-Note (2): If AllowToUpdateStatsFromBrowser parameter is set to 1 in AWStats config/domain file,
-you will also be able to run the update process from your browser. Just click on link "Update now".
-
-AWStats is a short for Advanced Web Statistics. It's a free powerful and featureful tool that generates advanced web (but also ftp or mail) server statistics, graphically.
-This log analyzer works as a CGI or from command line
-and shows you all possible information your log contains, in few graphical web pages.
-It uses a partial information file to be able to process large log files, often and quickly.
-It can analyze log files from IIS (W3C log format), Apache log files (NCSA combined/XLF/ELF log format or common/CLF log format),
-WebStar and most of all web, proxy, wap, streaming servers (and ftp servers or mail logs).
-Take a look at this comparison table for an idea on differences between most famous statistics tools for each features (AWStats, Analog, Webalizer,...).
-AWStats is a free software distributed under the GNU General Public License. You can have a look at this license chart to know what you can/can't do.
-As AWStats works from the command line but also as a CGI, it can work with major web hosting provider that allows CGI and log access.
-
-
-
-
-Features
-
- A full log analysis enables AWStats to show you the following information:
- * Number of visits, and number of unique visitors,
- * Visits duration and last visits,
- * Authenticated users, and last authenticated visits,
- * Days of week and rush hours (pages, hits, KB for each hour and day of week),
- * Domains/countries of hosts visitors (pages, hits, KB, 269 domains/countries detected),
- * Hosts list, last visits and unresolved IP addresses list,
- * Most viewed, entry and exit pages,
- * Files type,
- * Web compression statistics (for mod_gzip or mod_deflate),
- * Browsers used (pages, hits, KB for each browser, each version, 89 browsers: Web, Wap, Media browsers...),
- * OS used (pages, hits, KB for each OS, 34 OS detected),
- * Visits of robots (310 robots detected),
- * Search engines, keyphrases and keywords used to find your site (The 109 most famous search engines are detected like yahoo, google, altavista, etc...),
- * HTTP errors (Page Not Found with last referrer, ...),
- * Other personalized reports based on url, url parameters, referer field for miscellanous/marketing purpose,
- * Screen size (need to add some HTML tags in index page).
- * Number of times your site is "added to favourites bookmarks".
- * Ratio of Browsers with support of: Java, Flash, RealG2 reader, Quicktime reader, WMA reader, PDF reader (need to add some HTML tags in index page).
- * Cluster report for load balanced servers ratio.
-
- AWStats also supports the following features:
- * Can analyze a lot of log formats: Apache NCSA combined log files (XLF/ELF) or common (CLF), IIS log files (W3C),
- WebStar native log files and other web, proxy, wap or streaming servers log files (but also ftp or mail log files). See AWStats F.A.Q. for examples.
- * Works from command line and from a browser as a CGI (with dynamic filters capabilities for some charts),
- * Update of statistics can be made from a web browser and not only from your scheduler,
- * Unlimited log file size, support split log files (load balancing system),
- * Support 'nearly sorted' log files even for entry and exit pages,
- * Reverse DNS lookup before or during analysis, support DNS cache files,
- * Country detection from IP location (geoip) or domain name.
- * WhoIS links,
- * A lot of options/filters and plugins can be used,
- * Multi-named web sites supported (virtual servers, great for web-hosting providers),
-
- * Cross Site Scripting Attacks protection,
- * Several languages. See AWStats F.A.Q. for full list.
- * No need of rare perl libraries. All basic perl interpreters can make AWStats working,
- * Dynamic reports as CGI output.
- * Static reports in one or framed HTML/XHTML pages, experimental PDF export,
- * Look and colors can match your site design, can use CSS,
- * Help and tooltips on HTML reported pages,
- * Easy to use (Just one configuration file to edit),
- * Analysis database can be stored in XML format for XSLT processing,
- * A Webmin module,
- * Absolutely free (even for web hosting providers), with sources (GNU General Public License),
- * Available on all platforms,
- * AWStats has a XML Portable Application Description.
+
+
+
What
+is AWStats / Features Overview
+
+
+
+AWStats is short for Advanced
+Web Statistics. AWStats is powerful
+log analyzer which creates advanced web, ftp and mail
+server statistics reports based on the rich data contained in
+server logs. Data is graphically presented in easy to read
+web pages.
+
+
+
+Designed with flexibility in mind, AWStats can be run through a web
+browser CGI (common
+gateway interface) or directly from the operating system command line.
+Through the use of intermediary data base files, AWStats is able to
+quickly process large log files, as often desired.
+With support for both standard and custom log format definitions,
+AWStats can analyze log files from Apache (NCSA combined/XLF/ELF or
+common/CLF log
+format),
+Microsoft's IIS (W3C log format),
+WebStar and most web, proxy, wap and streaming media servers as well as
+ftp and mail server logs.
+
+See how the most famous open source statistics tools (AWStats, Analog,
+Webalizer) stack up feature by feature in this comparison
+table.
+
+AWStats is free software distributed under the GNU
+General Public License. The license
+chart illustrates what you
+can and cannot do.
+As AWStats works from the command line as well as a CGI, it is
+compatible with web hosting providers
+which allow CGI and log access.
+
+
+
+Features
+ AWStats' reports include a wide range of information on your
+web site usage:
+* Number of Visits, and number
+of Unique visitors.
+* Visit duration and
+latest visits.
+* Authenticated Users, and
+latest authenticated visits.
+* Usage by Months, Days of week and Hours of the day (pages, hits, KB).
+* Domains/countries (and regions, cities and ISP with Maxmind proprietary geo databases) of
+visitor's hosts (pages, hits, KB, 269
+domains/countries detected).
+* Hosts list, latest visits
+and unresolved IP addresses list.
+* Most viewed, Entry and Exit pages.
+* Most commonly requested File
+types.
+* Web Compression statistics
+(for Apache servers using mod_gzip or
+mod_deflate modules).
+* Visitor's Browsers (pages,
+hits, KB for each browser, each
+version, 121 browsers detected: Web, Wap,
+Streaming Media browsers..., around 500 with the "phone browsers" database).
+* Visitor's Operating Systems
+(pages, hits, KB for each OS, 35
+OS detected).
+* Robots visits, including
+search engine crawlers (351 robots detected).
+* Search engines, Keywords and Phrases used to
+find your site (The 116 most famous search
+engines are detected like Yahoo, Google, Altavista, etc...)
+* HTTP Errors (Page Not Found
+with latest referrer, ...).
+* User defined reports based
+on url, url parameters,
+referrer (referer) fields extend AWStats' capabilities to provide even
+greater technical and marketing information.
+* Number of times your site is added to Bookmarks / Favorites.
+* Screen size (to capture
+this, some HTML tags must be added to
+a site's home page).
+* Ratio of integrated Browser Support
+for: Java, Flash, Real G2 player,
+Quicktime reader, PDF reader, WMA reader (as above, requires insertion
+of HTML tags in site's home page).
+* Cluster distribution for
+load balanced servers.
+
+In addition, AWStats provides the following:
+* Wide range of log formats. AWStats can analyze: Apache NCSA
+combined
+(XLF/ELF) or common (CLF) log
+files, Microsoft IIS log files (W3C), WebStar
+native log files and other web, proxy, wap, streaming media, ftp and
+mail server log files. See AWStats
+F.A.Q. for examples.
+* Reports can be run from the operating system command line and from a
+web browser as a
+CGI (common gateway interface). In CGI mode, dynamic filter
+capabilities are available for many charts.
+* Statistics update can be run from a web browser as well as
+scheduled for automatic processing.
+* Unlimited log file size
+* Load balancing system split log files.
+* Support 'nearly sorted' log files, even for entry and exit pages.
+* Reverse DNS lookup before or during analysis; supports DNS cache
+files.
+* Country detection from IP location (geoip) or domain name.
+* Plugins for US/Canadian Regions, Cities and major countries regions, ISP and/or Organizations reports
+(require non free third product geoipregion, geoipcity, geoipisp and/or geoiporg database).
+* WhoIS lookup links.
+* Vast array of configurable options/filters and plugins supported.
+* Modular design supports inclusion of addition features via plugins.
+* Multi-named web sites supported (virtual servers, great for
+web-hosting providers).
+ * Cross Site
+Scripting Attacks protection.
+* Reports available in many international languages. See AWStats F.A.Q. for full list.
+Users can provide files for additional languages not yet available.
+* No need for esoteric perl libraries. AWStats works with all basic
+perl interpreters.
+* Dynamic reports through a CGI interface.
+* Static reports in one or framed HTML or XHTML pages; experimental PDF
+export through 3rd party "htmldoc" software.
+* Customize look and color scheme to match your site design; with or
+without CSS (cascading style sheets).
+* Help and HTML tooltips available in reports.
+* Easy to use - all configuration directives are confined to one file
+for each site.
+* Analysis database can be stored in XML format for use with external
+applications through XSLT processing.
+* A Webmin module is supplied.
+* Absolutely free (even for web hosting providers); source code is
+included (GNU General Public License).
+* Works on all platforms with Perl support.
+* AWStats has a XML
+Portable Application Description.
Requirements:
- To use AWStats, you need the following requirements:
- * Your server must log web access in a log file you can read.
- * You must be able to run perl scripts (.pl files) from command line and/or as CGI.
- If not, you can solve this by downloading last Perl version at ActivePerl (Win32) or Perl.com (Unix/Linux/Other).
- See AWStats F.A.Q. to have examples of supported OS and Web servers.
+AWStats usage has the following requirements:
+* You must have access to the server logs for the reporting you want to
+perform
+(web/ftp/mail).
+* You must be able to run perl scripts (.pl files) from command line
+and/or as a CGI. If not, you can solve this by downloading latest
+Perl version at ActivePerl
+(Win32) or Perl.com
+(Unix/Linux/Other).
+See AWStats F.A.Q. for
+examples of supported OS and Web servers.
