Table of Contents

  1. Introduction
  2. Download and install
  3. Creating your 1st analysis task
  4. Web Log Format
  5. Related learning resources

I. Introduction

This tutorial is your starting point for learning web log analysis. It
shows you some of the things you can discover about your visitors
through analysis of your web site logs. It uses Nihuo Web Log Analyzer
Windows version to provide examples of reports, but the knowledge gained
can be applied to Nihuo Web Log Analyzer Linux version and any other
traffic analysis tool.

II. Download and install

If you have not downloaded Nihuo Web Log Analyzer, please download and
install the latest version from

http://www.loganalyzer.net/download.html, before proceeding with this
tutorial.

III. Creating your 1st analysis task

1. Where can I find my IIS log files?

To determine where your IIS log files are stored, please follow below
guides step by step on your server:

  1. Go to Start -> Control Panel -> Administrative Tools
  2. Run Internet Information Services (IIS).
  3. Find your Web site under the tree on the left.
  4. If your server is IIS7
    1. Click Logging icon on the right
    2. On the bottom of logging page, you will see a box that contains
      the log file directory
  5. If your server is IIS 6
    1. Right-click on it and choose Properties.
    2. On the Web site tab, you will see an option near the bottom that
      says “Active Log Format” Click on the Properties button.

    3. At the bottom of the General Properties tab, you will see a box
      that contains the log file directory and the log file name.

2. Where can I find my Apache access log files?

The location and content of the access log are controlled by the
CustomLog directive. Default apache access log file location:

  • RHEL / Red Hat / CentOS / Fedora Linux Apache access file
    location – /var/log/httpd/access_log
  • Debian / Ubuntu Linux Apache access log file location -
    /var/log/apache2/access.log
  • FreeBSD Apache access log file location -
    /var/log/httpd-access.log

To find exact apache log file location, you can use grep command:

  • grep CustomLog /usr/local/etc/apache22/httpd.conf
  • grep CustomLog /etc/apache2/apache2.conf
  • grep CustomLog /etc/httpd/conf/httpd.conf

Sample output:

a CustomLog directive (see below)

CustomLog “/var/log/httpd-access.log” common

CustomLog “/var/log/httpd-access.log” combined

3. How to create my first analysis task?

Please visit online flash step by step tutorial in http://loganalyzer.net/log-analysis-tutorial/creating-project.html.

IV. Web Log Format

It is critical to set up your web server logging in a format that allows
Nihuo Web Log Analyzer to properly interpret the data and produce fully
detailed reporting.

1. Apache

By default, Apache generally logs in what’s called common log format,
and also provides an option to log in a more detailed format known as NCSA extended/combined log format. For optimal reporting, Nihuo strongly
recommend the NCSA extended/combined format. NCSA custom log format can
be analyzed by Nihuo Web Log Analyzer too.

2. Microsoft Internet Information Server (IIS)

Nihuo Web Log Analyzer can provide very basic reporting if your IIS log
files have, at the very least, the following fields:

  • date
  • time
  • c-ip
  • cs-uri-stem
  • sc-status
  • sc-bytes

However, this minimal logging does not provide enough information for
Referral and Browser reporting. Therefore it is advisable to set more
detailed logging properties for your IIS server.

For more detail report, please export following fields in your IIS log
files:

  • c-ip
  • cs-method
  • cs-host
  • cs-uri-stem
  • cs-uri-query
  • sc-status
  • sc-bytes
  • time-taken
  • cs(referer)
  • cs(user-agent)
  • cs(cookie)
  • cs-username
  • date
  • time
  • s-ip
  • s-port
  • sc-win32-status
  • sc-substatus
  • s-sitename
  • s-computername

V. Related learning resources

Post to Twitter Post to Yahoo Buzz Post to Delicious Post to Digg Post to Facebook