"I've really never used any log analyzing software before but I must say I am very impressed with Traffic [Report]. Setup really is very easy and the reports it generates are informative, easy to read and require very little setup on my behalf. It has already helped us to make decisions as to what areas we need to improve and what areas of our site work okay. I especially like the report that shows what site referred the user to our site. That's cool!!! Thanks again for all your help."
New in Version 1.2.1
- This update introduces a series of Page-based reports. These new reports include your visitors' most popular page requests, the pages of your site that may have stale links (complete with a listing of those links) and the most error-prone pages.
- The URL report now includes a second section which displays the URLs sorted by error.
- Several operations now enjoy improved threading (computer responsiveness) and/or speed.
- This update introduces a redesigned Report Cache. In earlier versions, the Cache contained the information displayed in your reports. This was a problem, since changing the settings that affect your reports (such as date ranges, categories and enabled/disabled reports) would not retroactively affect information already in the Cache. The old desig also required that each of your domains have its own cache file. The redesigned Cache changes all this. It stores encoded entries from your logs. Since it does not store actual report data, it won't go stale if you make settings changes. And, if you wish, all your domains can share the same Cache file.
- Improved DNS look-ups. In earlier versions, Traffic Report would force your reports to wait for the look-ups to complete. This could be a timely process. In this update, look-ups take place in the background. They will then appear in subsequent reports. As before, the Cache automatically rechecks successful look-ups every 18 weeks and retries failed look-ups every 6 weeks.
- Traffic Report will automatically update Caches from earlier versions as needed.
- Bug fix. If your log entries contained a visitor's DNS, followed by its IP address, and you had DNS look-ups turned on, the visitor's name would appear blank in the reports. This has been corrected.
- You can now specify a creator application for your report's pages. (Previous versions, by default, made SimpleText the pages' creator, allowing you to only change the images' creator.) Your report's pages and images can have different creators, if you wish. The creator is specified by a four-digit code. You can type this in if you happen to know it, or select the Application itself by clicking the "Set" button (which is much easier). This setting is found in the HTML Report Odds & Ends panel in the Preferences window.
- The Search Args and Path Args now always appear in their corresponding reports. (In earlier versions, if the user had requested the Args be treated as part of the URL, they didn't appear in their dedicated report as well.)
- URLs appearing in graphs now include domain information, if available. If they need to be truncated, this is done in the middle to preserve the topmost directories and the name of the file itself.
- Corrected a bug affecting some earlier versions of Traffic Report. The error statistic was mistakenly reported as violations. The violation statistic displayed only the errors and did not include actual violations.
- Enhanced options to control which date range is covered in your reports. Now you can have the reports display information for the last "N" days, where "N" is a number of your choosing. For instance, the last 365 days. This would be helpful for clients who wish to view a year's worth of activity. This option is available in the Record Scope preference panel. This panel also includes some usability improvements; clicking the up or down arrow next to a blank date field will display tomorrow's or yesterday's date.
- Corrected a bug in the Record Scope preference panel. Occasionally it
would mishandle times by confusing 12:00 PM with 12:00 AM.
- The "!!Bad URL Reference..." and "!!SMTP: Couldn't say FROM" WebSTAR log directives are now recognized. Previously, Traffic Report had mistakenly reported these as "bad lines."
- Traffic Report now recognizes an alternate end-of-line marker that is not ordinarily found in WebSTAR logs. (Such a marker may be introduced by some log post-processors.)
- Log entries are now assumed to qualify as a Hit if they do not contain information saying otherwise. This way, if your log does not contain a result code (such as 200) or a named result (such as "OK") you won't get a zero hit count in your reports.
Improved reporting on the page requests your visitors make. The following reports now display Page statistics:
- Day-by-Day Stats
- Agent Stats (& graph)
- Primary Domains by Agent
- Directories (& graph)
- Primary / Secondary Domains
- Primary / Secondary Domains by OS
- Referrer Stats
(Having this information in the Directories report may be especially useful if some of your directories represent sites you host.)
(Note on Primary / Secondary Domains by Referrer reports: these reports now use a new method to calculate page requests. Previously, page requests reflected the requests made during the visits displayed in the column immediately to the left. So these page requests were associated with the visit initiated by the referrer, rather than with the referrer itself. The new method ties the page requests not to a particular visit, but directly to the referring page of the page request.)
- Traffic Report is friendlier in the way it guides you to make required settings, such as selecting your logs. Rather than graying out the Update HTML Report button, this button is now always clickable. If logs have not been selected, you are told this and taken to the corresponding panel of the Preferences window.
- If, when Traffic Report opens your document file, it can't find the folder you have indicated you wish your report or its cache file to be stored, Traffic Report reverts to using the default folder for this (Traffic Report's own folder).
- Important Note: This update of Traffic Report is incompatible with cache files produced by earlier versions. If you've enabled the cache for your reports, Traffic Report will rename your old cache files (which you can delete) and create new ones.
Traffic Report can now automatically recognize your log's format. This option is available in the Log Structure preference panel and is activated by selecting "Auto-Detect" from the Server Software popup menu. For newly created settings documents, this option is on by default. This simplifies configuring Traffic Report since you don't have to specify your server software.
The Log Location Panel's "Add File" button now allows selection of
files regardless of their file type (in case your log isn't marked as
being a TEXT file type).
Consistent look to folder icons in the Preferences window.
Fixed broken icons appearing in the Scheduler, Domains and Preferences
windows. [OS X version only]
Fixed phantom bug #-50 in DNS Look-ups. [OS X version only]
Improved error reporting for file IO operations. This ensures that when saving a Document, if something goes wrong a message will always appear telling you so.
Bugs Fixed in This Version
Corrected a problem with the graphs' increment lines. Due to a rounding error, these lines would sometimes appear a few pixels away from where they should have been. In some cases this was beyond the X or Y axis. They now are accurately displayed
The layout directives that appear in WebSTAR logs tell Traffic Report about the kind of information the log contains. Occasionally, when reading unusually long directives of this kind (such as one describing 30+ columns), the line would get cut off. This could cause Traffic Report to disregard some of the rightmost columns in your log. This bug has been eliminated.
When Traffic Report reads Japanese FileMaker Pro logs, it reports error messages within the log as if they were bad lines. This has been corrected; it now recognizes these lines as messages.
Known Bugs and Incompatibilities
Some beta testers have reported that the popup buttons in TR become invisible when using Kaleidoscope version 1.8. Updating to Kaleidoscope 1.8.2 or later solves this problem.