Configuring "Analog" to Process Log Files

∟Analog - Web Server Log Files and Analysis Tool

∟Configuring "Analog" to Process Log Files

This section provides a tutorial example on how to configure 'Analog' to process Web server log files.

With "analog" installed, now I need to run it against my log files. My Web site is hosted by an ISP. They put log records one file per week. The log files are zipped with gzip tool. The following is my experience of configuring "analog" to run on log files.

1. Reading "analog" documentation at c:\local\analog\docs\index.html.

2. Setting up and running "analog" to run in my log directory:

herong> edit c:\local\analog\analog.cfg
   LOGFILE c:\local\logs\logfile.log
   OUTFILE c:\local\logs\report.html

herong> mkdir c:\local\logs
herong> cd c:\local\logs
herong> copy c:\local\analog\logfile.log .
herong> mkdir .\images
herong> copy c:\local\analog\images\*.* .\images

herong> c:\local\analog\analog
   (no errors)

herong> dir 
    2,635 code.png
    3,141 dir.png
    8,470 logfile.log
    3,633 org.png
    2,466 os.png
    4,519 ref.png
   24,109 report.html
    3,905 req.png
    2,732 size.png
    3,060 type.png

Notice that in this step, I changed the configuration file, analog.cfg, to specify where my log file is, and where the out file should be stored.

Also notice that "analog" not only generates the report file, report.html, it also generate a number of *.png files. I guess those *.png files are used to store statistic data that can be added to future log files.