Interpreting Webalizer Reports

The first page
On this page, you'll see a graph such as this:

Usage summary for arrgh.net

This is a summary view of the past 12 months, for comparison purposes. You'll be able to see long term trends in your web traffic at a quick glance.

The next (and last) thing of interest on the first page of your webalizer report is a table which summarizes each month for which you have run a webalizer report, and which gives both daily averages and monthly totals for Hits, Files, Pages and Visits, as well as the monthly total in Kilobytes*.

Summary by Month
Month Daily Avg Monthly Totals
Hits Files Pages Visits Sites KBytes Visits Pages Files Hits
Jul 2004 55 13 2 1 97 7627 42 64 423 1718
Jun 2004 629 263 9 3 114 157292 105 274 7896 18876
May 2004 49 22 2 1 112 40322 51 76 665 1498
Apr 2004 5 3 1 0 51 4714 24 34 118 160
Mar 2004 6 2 1 1 56 98 33 37 78 210
Feb 2004 13 4 1 1 73 1434 35 40 126 384
Jan 2004 12 9 1 1 55 466 35 49 294 380
Dec 2003 24 4 2 1 50 1192 44 62 148 732
Nov 2003 24 3 1 1 63 284 42 50 92 728
Oct 2003 89 55 3 1 58 28154 56 112 1708 2788
Sep 2003 17 14 1 1 19 450 37 47 422 516
Aug 2003 8 6 1 1 24 2797 34 42 208 272
Totals 244830 538 887 12178 28262

Each month in the left hand column is a link to a more detailed breakdown of that month's traffic.

The Details

The data being presented to you takes the form of Hits, Files, Visits, Sites, Pages, Kilobytes, URLs, Referrers, User Agents and Response codes. All of these data are generated by interpreting a series of web transfers as logged by our Apache web servers. Apache creates a line such as this:
66.196.90.216 - - [12/Aug/2004:04:02:03 -0400] "GET http://www.arrgh.net/music/data.php?composer_name=Gorecki HTTP/1.0" 200 659 "-" "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)"

Each such line breaks down to the following data:

  1. Internet address of the machine visiting your site
  2. The date, time, and time zone as an offset from GMT
  3. The specific request. In most cases, this will be GET, but there may also be POST and HEAD requests.
  4. The URL being requested
  5. The HTTP protocol used for the request
  6. The response code
  7. The number of bytes transferred
  8. The referring page
  9. The user agent

From this data, webalizer crafts various views of your web traffic.

Definitions

* You cannot use the Kbytes as reported by webalizer to check your billed transfers. Panix uses web accelerators known as Squids. The squids cache pages and, if the actual page has not changed, serves the page from it's cache rather than the web server. In the process of doing this, duplicate log entries are created for a File; one for the squids and one for the web server. The web server log entry will not show any bytes transferred, however, so you need to get squid logs as well as web logs to check on bytes transferred. This can be done using the '-a' switch to getlogs. We do not do this by default for webalizer processing because the duplicate log entries would render the rest of Webalizer's statistics grossly inaccurate.


Last Modified:Wednesday, 30-Jan-2013 12:14:11 EST
© Copyright 2006-2011 Public Access Networks Corporation