Web log analysis
Our web log system runs each night at midnight, and processes your web access logfiles in a way you specify.
If you have subdomains pointed at the same account
then you should use your alias (which should be provided when you register
or can be found at with the CGI I will write soon ;-)) as a suffix to
.processlogs for those domains.
If you do not create one then a .processlogs will be checked.
Each command goes on a line by itself. Our web log system will object if you do not specify the file correctly. It will mail firstname.lastname@example.org who will probably fix your file and tell you why it broke.
- This command will resolve all the IP addresses which are
resolvable via DNS and substitute the numbers for host names. It is useful
to run this before you run analog or webalizer or even before you send the
logs to yourself since it means that you get logs you can read more
If you use this command it must appear first in the file.
- SEND [WHAT] TO [WHOM]
- This command will allow you to send raw or processed logs to
[WHAT] can be either RAWLOGS, ANALOG_TEXT, or ANALOG_HTML
[WHOM] should be an email address or a list of email addresses split by commas.
- PUT [WHAT] IN [WHERE]
- This command will allow you to put raw or processed logs in
a directory under your home directory
[WHAT] can be either RAWLOGS, ANALOG_TEXT, ANALOG_HTML, or WEBALIZER_HTML
NB You CANNOT send WEBALIZER_HTML due to the way it is processed (incrementally adding to a bigger picture of stats). Also you may only include ONE PUT command for this. If you would like it to show up in more than one place then please mail us, or use symlinks.
[WHERE] should be a path from your home directory starting with ~
This can include somewhere under ~/www/www.example.org so that you can show people your stats.
The PUT and SEND lines may be interleaved in any order you like. We recommend that you place similar lines together however to avoid your confusion.
If you don't have a .processlogs file in your directory then it will default to doing nothing at all.
Here is a sample .processlogs file we use for testing.
Configuring the tools
If you want to configure analog or webalizer you may do so by placing an analog.conf file in your home directory or by placing a webalizer.conf file in the directory in which you run webalizer. (i.e. whatever you have after PUT WEBALIZER_HTML IN)
The webalizer documentation to refine your config is available.
The documentation for analog is also available.
Here is the default webalizer.conf
Here is the default analog.conf
If you intend to run webalizer or analog you will want to at least put your domain name into those files and copy them to your home directory (for analog) or the final directory of output (for webalizer).
- Support Index
- Hosting accounts
- HTTPS hosting
- Sender Rewriting Scheme (SRS)
- Spam filtering
- Sphinx shell accounts
- Web and Email hosting
- Control Panel
- DNS Settings
- HTTPS and TLS
- Hosted domains
- Mail Auto-Responders
- Shell access
- Uploading files
- Usage logs
- Web applications
- Web logs