W3Olista - Online WWW Statistics

W3Olista is a program that takes the logfiles of your local WWW server, analyzes them and prints out reports about its usage. The most important feature is that it produces these reports online. You can browse your statistics with your favourite WWW browser, and actually zoom into them simply by clicking on any item.

The features in short

The program reads in daily, monthly, or full logfiles (even combined). With daily or monthly files, only the necessary files are scanned, greatly improving the program's performance.
Logfiles may also be compressed or gzip'ed, in which case they're transparently uncompressed on-the-fly.
A wide variety of date selections is supported, from Last 24 Hours to Custom Dates.
Reports can be produced either by filling out an online input form, by calling specially constructed URLs, or from the command line (enabling offline reports and the usage from cron).
Happily munches proxy or cache logs and still produces something remotely usable.

Stuff to Read

Are you ready for W3Olista? Read about the requirements your system must fulfill. They should be pretty standard today.
W3Olista Installation instructions.
A little Introduction with some basics you should know about the program.
Operating the program via the Query Form.
Creating statistics with Custom URLs and offline statistics from the Command Line (or via cron) are described in the Operation manual of the program.
Please read the License before installing this software.
If you can't get W3Olista up and running, read this Troubleshooting guide.

If I don't need to talk any further, you should probably get the source code right now.

In the Future ...

The possibility to protect the program, so that normal users can only access a limited amount of features (like only daily reports).
Graphics, like pie charts of the top-level domains that have accessed your site, or bar graphs of the monthly access distribution.
More sophisticated selections, probably in an SQL-like manner ("Report all access from hosts that have read at least 3 pages of our 'hello' subdirectory").
Report caching in temp files could save a lot of time when browsing reports.
Do you have more ideas? Tell me!

Remember that further development is unlikely if I don't get any feedback or other proofs that this software is really used.

Problems & Bugs

All sizes are recorded in 512 byte chunks, and fractions are discarded. You can transfer as many files below this size as you want, they will always get reported with zero size.
Sizes will also be reported incorrectly if total transfer exceeds one terabyte.
If you go clickedy-click through a browseable report, memory usage is way below optimum. This is unlikely to change.
Because the average Web server is much too smart and accepts some malformed requests, sometimes invalid File Links may be printed.

Frank Pilhofer <fp -AT- fpx.de> Back to the Homepage

Last modified: Wed Apr 12 21:37:03 1995