Awstats

Apache Logs (Awstats)

The Apache httpd.conf directive "LogFormat" defines a log formatting that can then be referenced using its name. The following 2 examples define the log formats named: "combinedv" and "combined".

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %V" combinedv
CustomLog pathtoyourlog/yourlog.log combinedv

Or the standard NCSA combined/XLF/ELF format (this format should already be defined in the distribution httpd.conf file).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" combined
CustomLog /yourlogpath/yourlogfile combined

The CustomLog item is required, if you want to use a specified LogFormat and save the logs in a specific folder. Usually webmasters will want to save logs for each site in the appropriate "site" folder.

Using Awstats to analyse Serv-U logs

You will need the tool ServuEvent.dll (you can download it here:  http://ftpservertools.tripod.com/downloads.htm ).
Thanks to FTPServerTools for being a great help.

1) Here is a basic summary of the install:
a) Copy Servuevent.dll to your Serv-U install folder.

b) Add the following, at the end, of your ServUDaemon.ini:
[EXTERNAL]
EventHookDLL1=Servuevent.dll

IIS logging with Awstats

LogFormat
Version : 2.1+
3.1+ for tags %host,%logname,%time1,%time2,%methodurl,%methodurlnoprot,%method,%url, %query,%code,%bytesd,%refererquot,%referer,%uaquot,%ua,%other
3.2+ for tags %gzipin,%gzipout
4.0+ for tags %gzipratio,%syslog
4.1+ for tag %virtualname
5.6+ for tag %deflateratio
6.1+ for tag %time4
6.2+ for tag %time3

Apache Preferred Awstats Custom Log Formats

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %V" combinedv

"Remote host" "Remote logname" "Remote user" "Time the request was received" "First line of request" "Status" "Size of response in bytes" "Referer" "User-Agent" "The server name"

IIS Optimizing logging for Awstats & reduce logs size by over 50%!

High traffic sites can easily get daily logs over 100MB. It can be very beneficial to log only the information we actually use. We will require the minimum logging for decent Awstats reports. We will copy the recommended Apache LogFormat:
"%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %V"

For more details on the meaning of these values see: Apache Preferred Awstats Custom Log Formats.

Serv-U logs analysis with Awstats: Design Document

Update: For a simple and immediate solution see: Using Awstats to analyse Serv-U logs

Using Awstats to monitor Serv-U the FTP Server from Rhino Software.
After investigating this a "bit", it appears we will have to write a process/script/app that will read the Serv-U logs and convert then to a format that Awstats can read. This is not difficult but probably a few days of effort. In this document, I will outline the design. Maybe some kind "angel" programmer will offer to write it. In any case if I get something that works, I will post it here.