Logan Pro Users Manual
(c) 1999-2004 SB-Software
Thank you for choosing Logan Pro, the Internet's premier log analysis tool!
Table Of Contents
Quick Start
Description
Getting Started: The Job Window
Creating and Editing Jobs
Registration
Contact the Author
Revision History
This manual describes the Windows GUI version of Logan Pro. The Windows version is compatible with all modern versions of Windows, including 95/98/ME/NT/2000/XP. Logan Pro is also available as a Linux version and as a Windows Console-Mode application.
The Windows GUI version of Logan Pro offers an easy to use job-oriented interface. You may define multiple jobs to support multiple websites, and then run the jobs as you see fit. The GUI job editor is user-friendly and easy to use and lets you set all of the parameters for the job. Logan Pro is multithreaded, providing for fast efficient operation and snappy user interface response.
To get a quick feel for how Logan Pro works, lets start by running the sample job:
- Start the Logan Pro application
- Hilight the "Sample" line in the Jobs: list
- Press the <Run Job> Button
- At this point, Logan Pro will begin to analyze the log file. The status window will be displayed and numbers should start counting as days, weeks, months, etc are processed.
- Patiently wait for the job to complete!
- When the job has completed, the button at the end of the status window will change to "Job is Complete -- Click here to view"
- Press the "Job is Complete" button in the status window
- The status window will disappear and your browser will pop up with the report.
Getting started: The Job Window
Logan Pro is a Job Oriented log analyzer. A Job represents the task of analyzing a log file and generating reports. There are two instances where you might have multiple jobs:
- If you have multiple websites, create a different job for each website.
- If you want to create multiple reports for a single website, create a job for each different type of report.
When you first load Logan Pro, it displays the Job Window. The Job window lists all of the jobs that are available (when you first install the program, a sample job will be listed in the window)
You can do the following operations in the job window:
New Job
Pressing the New Job button will create a new job for you. The first thing you'll need to do is to enter a new name for your job -- try to think of something descriptive. You'll also want to enter the input file specifications for your log file.
Edit Job
This will bring up a similar dialog as the New Job button. It allows you to edit the preferences of an existing job.
Delete Job
Pressing this button deletes a hilighted job.
Run Job
This button will execute the currently hilighted job.
View Report
If the hilighted job has a report available (i.e. by prior use of the <Run Job> button), then pressing this will bring up the previously generated report.
The Job Editor contains all parameters specific to a job. Access the job editor by using the <New Job> button to create a new job, or by using <Edit Job> to edit an existing job.
Logan Pro is a shareware program, and thus you must register it to continue using it. See the Logan Pro website at http://www.loganpro.com/ for more information.
You may email the author at smbaker@loganpro.com.
- Version 1.0
- Inital public release
- Version 1.1
- Added search query reports
- Added glossary
- Fixed logan.dns file showing up in directories other than Logan's root
- Added registration nag screen and registration entry screen
- Fixed last field of some IIS logs being ignored
- Version 1.2
- Fixed connectivity of years in calendar if a year in the middle is missing
- Fixed january not displayed correctly in calendar
- Added exclude filter settings
- Version 1.3
- Added detailed directory stats
- Added referer and search info to detailed file/dir stats
- Fixed problem with DNS resolver crashing if hostent->h_name == NULL (seems to me this shouldn't have happend, but...)
- Fixed job report type not being saved in job editor
- fixed occasional crash on non-log input lines
- Fixed occasional invalid date (12/31/79 or 1/1/80) reported from non-log input lines
- Changed TIndices in DateData/DetailFileData from statically allocated to dynamically allocated to save memory
- TIndices now allocated on demand (for all DateData, and for marked DetailFileData).
- Version 1.4
- Reject apache format log lines with parsed dates of -1
- Increased read buffer size to handle longer lines
- Log bad lines to "badlines.txt" in report directory
- Added reject bad dates advanced option
- Sort the items in the job list
- Preserve the hilighted item in the job list when it's edited
- Fixed problem with log entries that happen at 0 minutes after the hour in IIS logs
- Fixed overflow on report lines with > 6.5 million hits
- Version 1.5
- Added delete report command
- Fixed report display to not scroll when it is updated
- Classify URLs that end in '/' as pages, not files
- Version 1.6
- Added file and refer-site tables to detail referer page
- Fixed delete report button not anchored to bottom of form
- Replaced file read mechanism w/ buffered reader mechanism
- Added log file statistics
- Consider .shtml files to be pages (in addition to .html files)
Copyright (c) 1996-2003 SB-Software
smbaker@loganpro.com