Analog hit report has several parts to it. It is easiest to look at each section separately.

Headers

The Headers describe when the report was run and how long a time period the report covers. They can also contain special announcements about changes to the web server.

The example report we are using is for www.quake.gwi.net, and is a monthly report for October.

Web Server Statistics for www.quake.gwi.net
===========================================

Program started at Mon-01-Nov-1999 02:24.
Analyzed requests from Fri-01-Oct-1999 11:02 to Sun-31-Oct-1999
22:24 (30.5 days).
-----------------------------------------------------------------

General Summary

The general summary displays the totals of all the other sections, to give you a quick overview of website activity. As the report says, the numbers in the parentheses are details for a different time period, in this case, the last 7 days of the month. Let's detail what each line is talking about:

• Successful Requests — The number of separate requests for files from the server. Each page often contains multiple files. (Example: home.html has a background of back.jpg, and title of title.jpg, it is one page, but loading it counts for 3 successful requests.)
  
• Average Successful Requests per Day — The average number of requests for files per day.
  
• Successful Requests for Pages — The number of separate requests for pages. A page is the actual HTML file.
  
• Successful Requests for Pages per Day — The average number of requests for pages per day.
  
• Failed Requests — These are requests for files that don't exist in your website. A few of these are normal. If you have a lot, make sure that all the links in your HTML pages are correct.
  
• Redirected Requests — If you have a page that has a redirect coded into it, the server keeps track of that.
  
• Distinct Files Requested — This is the number of different filenames on the server that were accessed.
  
• Distinct Hosts Served — The number of different computers on the Internet who accessed the site.
  
• Unwanted Logfile Entries — This is a measure of the number of lines in the logs that analog cannot read. Nothing to worry about unless it gets very large.
  
• Data Transferred — The amount of information sent out to visitors by the server. In this example, 3.3 GB were transferred. GWI does charge for the amount of transfer from the site based on your VWS account type. Please see our Advanced Services page for details.
  
• Average Data Transferred per Day — The amount of information transferred from the site each day.

General Summary
---------------
(Figures in parentheses refer to the 7 days to 31-Oct-1999 23:59).
Successful requests: 4,425 (1,279)
Average successful requests per day: 145 (182)
Successful requests for pages: 921 (259)
Average successful requests for pages per day: 30 (36)
Failed requests: 499 (45)
Redirected requests: 11 (1)
Distinct files requested: 11 (9)
Distinct hosts served: 800 (249)
Unwanted logfile entries: 1
Data transferred: 3,345,461,596 bytes (946,074,579 bytes)
Average data transferred per day: 109,782,250 bytes (135,153,511 bytes)
-----------------------------------------------------------------

Monthly, Weekly, Daily, Hourly, Quarter-Hour and Five-Minute Reports

The Monthly, Weekly and Daily reports show a comparison of the number of hits by the indicated time period. The example shown displays a comparison of the number of hits during different weeks. As this report is only analyzing data from the first of the month, the week beginning September 26th is not complete. As the report was generated on the 1st of November, the report for the week starting October 31st is also incomplete.

The Quarter-Hour and Five minute reports are disabled by default. If you wish them enabled, please let us know and we can do so.

Weekly Report
-------------
Each unit (+) represents 8 requests for pages, or part thereof.

week beg.: #reqs: pages:
---------: -----: -----:
26/Sep/99: 159: 40: +++++
3/Oct/99: 585: 142: ++++++++++++++++++
10/Oct/99: 936: 187: ++++++++++++++++++++++++
17/Oct/99: 1320: 261: +++++++++++++++++++++++++++++++++
24/Oct/99: 1171: 238: ++++++++++++++++++++++++++++++
31/Oct/99: 254: 53: +++++++

Busiest week: week beginning 17/Oct/99 (261 requests for pages).
-----------------------------------------------------------------

User Reports

If part of your website is protected by a password (using .htaccess) then you will have a user report showing the logins. For information about setting up .htaccess to password protect parts of your site, please see our instructions.

User Report
-----------
Listing users, sorted by the number of requests.

#reqs: %bytes: user
-----: ------: ----
13: 100%: username
-----------------------------------------------------------------

User Failure Report
-------------------
Listing users, sorted by the number of failed requests.

#reqs: user
-----: ----
87: username
-----------------------------------------------------------------

Domain Report

For our example site, we do not have domain reports turned on. Not all of our virtual web servers can have domain reports enabled at the moment. What a domain report does is report about who accessed your site, from where. If it were turned on, it would show you the percentage of visitors from gwi.net, maine.rr.com, cybertours.com, etc. As domains are not linked to a physical location, you cannot track what state people are in. If you get enough international traffic this report can tell you which countries visit your site most often.

If you want to find out if this option is available for your site, please feel free to email us at webmaster@gwi.net.

Domain Report
-------------
Listing domains, sorted by the amount of traffic.

#reqs: %bytes: domain
-----: ------: ------
4425: 100%: [unresolved numerical addresses]
----------------------------------------------------------------

Host Report

The host report lists individual computers if they have accessed your site multiple times. Because this site does not have Domain Reports turned on, the report just lists IP addresses. Combined with the Domain Report, this can help you to find out if one person from GWI is visiting your site a lot, or several different people are visiting. It isn't foolproof, as several people behind a firewall will show up under only one host listing.

Host Report
-----------
Listing hosts with at least 10 requests, sorted alphabetically.


#reqs: %bytes: host
-----: ------: ----
10:  : 24.234.0.7
15: 1.05%: 62.100.0.146
12: 0.40%: 62.104.197.10
12: 0.30%: 128.122.225.16
10:   : 129.130.98.139
17: 0.57%: 130.226.80.138
10:   : 132.203.83.57
12: 1.09%: 134.115.68.21
12: 1.70%: 139.175.56.71
11: 1.05%: 151.188.43.19
17: 0.02%: 161.142.78.86
10:   : 165.21.83.140
15: 0.55%: 170.141.7.197
18: 0.03%: 192.169.41.47
10:   : 193.113.242.52
10:   : 195.90.19.103
17: 0.56%: 198.200.139.3
10:   : 199.72.211.111
220: 9.15%: 199.244.145.6
...
3496: 75.97%: [not listed: 751 hosts]
-----------------------------------------------------------------

Directory Report

The directory report shows the amount of transfer from each directory in the website. If you organize your page with different subdirectories, you can use this part of the report to see which directories have the most requests, and the largest data transfer.

The example report shows only 2 directories. The root directory (where the main page lives) and the /files directory. And while you can see that the root directory has many more requests, it accounted for very little traffic. The /files directory had fewer requests, but most of the transfer. The reason for this is that the size of the files in the /files directory were much larger than those in the root directory.

Directory Report
----------------
Listing directories with at least 0.01% of the traffic, sorted by
the amount of traffic.

#reqs: %bytes: directory
-----: ------: ---------
526: 99.66%: /files/
3885: 0.34%: [root directory]
14: : [not listed: 1 directory]

File Type Report

The file type report lists the amount of transfer by file type. Analog uses the extension at the end of the file name to determine the file type. Be aware that this is case sensitive, so .GIF will be listed separately than .gif.

The example report shows that almost all of the data transfer for the site was from .exe files. If our goal were to lower the amount of bandwidth used by this site, we might want to consider linking to other sites that had the files people needed, rather than placing them on our site. Gif files had the next highest transfer, and .html files don't show up in the list at all, meaning that they accounted for less than 0.1% of the total traffic on the site this month.

File Type Report
----------------
Listing extensions with at least 0.1% of the traffic, sorted by
the amount of traffic.

#reqs: %bytes: extension
-----: ------: ---------
526: 99.66%: .exe
2978: 0.29%: .gif
921: 0.05%: [not listed: 2 extensions]
-----------------------------------------------------------------

File Size Report

The file size report lists the number of requests and percentage of transfer based on file size. Once again, this can be very useful if you are trying to lower the amount of bandwidth used on your site, by showing you what size files are hit most often.

In our example, you can see that most of the traffic comes from files of 10MB or larger. This is not normal for most websites.

File Size Report
----------------
size: #reqs: %bytes:
-----------: -----: ------:
0: 622: :
1b-10b: 0: :
11b-100b: 0: :
101b-1kb: 1: :
1kb-10kb: 3392: 0.34%:
10kb-100kb: 99: 0.15%:
100kb-1Mb: 90: 1.24%:
1Mb-10Mb: 85: 10.48%:
10Mb-100Mb: 136: 87.79%:
-----------------------------------------------------------------

Status Code Report

The status code report shows you the different HTTP result codes generated from people accessing your site. There are only a couple of codes that you can change anything with.

• Partial Content — This indicates that the visitor was unable to download the entire page they were viewing. There could be several reasons for this. Their modem connection dropped, the information they were view wasn't formatted well for their browser, or the file they were trying to view was not complete.
  
• Document Moved Permanently — This comes from having a redirect page, or server symlink that moves the visitor's request to another page.
  
• Not Modified Since Last Retrieval — If a visit or has caching enabled in their browser, and is a repeat visitor, their browser may decline to download a file after discovering it has not changed. That is what this measures.
  
• Authentication Required — This indicates that the page or are that the visitor was trying to view required a password, and they entered the password incorrectly.
  
• Access Forbidden — This message comes up when the server does not allow the visitor to view the file or directory in question. Usually this is due to the file permissions being too secure.
  
• Document Not Found — This error usually occurs due to typos. Someone entering home.html instead of home.htm. If there are a lot of these errors, it could mean one of your links is bad, or that a search engine is listing a file that no longer exists on your server.
  
• Request Timeout — This usually occurs when the visitor is on a slow connection, and their system stops responding to the server.

Status Code Report
------------------
Listing status codes, sorted numerically.
#reqs: status code
-----: -----------
3817: 200 OK
106: 206 Partial content
11: 301 Document moved permanently
502: 304 Not modified since last retrieval
23: 401 Authentication required
2: 403 Access forbidden
468: 404 Document not found
6: 408 Request timeout
-----------------------------------------------------------------

Request Report

The request report shows which files were the most popular. Towards the bottom of the example, you see the file isdn.html. Keep in mind that as an html file, it might include background images or other files when it loads, which are not represented here.

Request Report--------------
Listing files with at least 20 requests, sorted by the number of
requests.
#reqs: %bytes: last date: file
-----: ------: ---------------: ----
852: 0.04%: 31/Oct/99 22:24: /
751: 0.16%: 31/Oct/99 22:24: /mainlogo.gif
745: 0.03%: 31/Oct/99 22:24: /mainright.gif
745: 0.03%: 31/Oct/99 22:24: /mainleft.gif
737: 0.07%: 31/Oct/99 22:24: /q3a_logo2.gif
350: 61.63%: 31/Oct/99 21:00: /files/csb31full.exe
152: 31.31%: 31/Oct/99 14:36: /files/q3test_win32_1_08.exe
55:   : 31/Oct/99 13:14: /isdn.html
38: 6.73%: 31/Oct/99 14:36: [not listed: 3 files]
-----------------------------------------------------------------

Redirection Report

The redirection report can be confusing. In the example below, the redirects are caused by users entering in the URL slightly incorrectly, and the server fixed what they typed. Both turkey and files are actually directories, which is signified by adding a / to the end of the name when entering them in the address area. Since the server views files and directories in different ways, it tried looking at the directories as files first, and then realizing they were actually directories, redirected the request to the directories.

Redirection Report
------------------
Listing files, sorted by the number of redirected requests.
#reqs: file
-----: ----
9: /turkey
2: /files
-----------------------------------------------------------------

Failure Report

The failure report lists filenames that were requested, but did not exist. Check your site design to make sure that all of the links work, as a bad link within the site can cause this. As mentioned before, search engines will sometimes store old information about your site, and people using them will try to open files that no longer exist.

Most everyone will see the file robots.txt listed here. Robots.txt is a file that webcrawler searches look for that help them index your site more accurately. More information about how robots work can be found at the Robot's Exclusion page.

Failure Report--------------
Listing the first 30 files by the number of failed requests,
sorted by the number of failed requests.
#reqs: file
-----: ----
117: /new/
45: /robots.txt
24: /turkey/mainlogo.gif
24: /turkey/mainleft.gif
24: /turkey/q3a_logo2.gif
24: /turkey/mainright.gif
22: /new/files.html
15: /favicon.ico
13: /files.html
11: /new/join.html
11: /help.html
10: /home.html
8: /join.html
8: /players.html
7: /how-install.html
7: /turkey
7: /schedule.html
6: /links.html
6: /new/players.html
6: /new
5: /faq.htm
5: /whatis.html
4: /files/UTDemo348.exe
4: /players/sandman.htm
4: /q2compics.htm
4: /new/help.html
3: /players.htm
3: /files.htm
3: /schedule.htm
3: /players/kibbles.htm
60: [not listed: 34 files]
-----------------------------------------------------------------