Log file options tell Analyzer how to handle the processing of log files, as follows:
Do not display text after pound (#) key in URL
The pound (#) key is used in URLs to denote sections within HTML documents (at anchors, for example). This is often not relevant, and FastStats Analyzer can automatically remove it. If you don't remove it, index.html#par3 will be counted as a separate page from index.html.Do not display text after the question mark (?) in URL
Forms (most notably, search engines), use the question mark to transmit data to and from the server. This information is often not relevant, and FastStats Analyzer can automatically remove it. If not removed, then references to one page with different query strings will appear as separate pages in your reports. Some sites depend upon query string values to distinguish between separate pages.If you have tracked files, and you tell Analyzer not to ignore query string variables, then the query string report under the tracked files report will be blank, and Analyzer will track references to the file along with the query string values. To track just the file accesses, simply use a wildcard on the end of the tracked file name (to match all the possible query string). For example, you can track " /index.html* " with a wildcard on the end to match all the potential query strings that might show up there.
Only include log file records if all include filters are true
Check this box if you want to AND the result of all include filters together.Only exclude log file records if all exclude filters are true
Check this box if you want to AND the result of all exclude filters together.Case sensitive handling of all Filenames, Referring URLs, Domain Names, etc.
If this box is checked, /DIRECTORY will be treated differently than /directory. If not checked, Analyzer converts to lower case all referrer test and requested filename text, as well as all text used in filters, so that the matching is not case sensitive. (Converting to lowercase once allows for faster processing than performing a case insensitive match with every filter.)All log files are in European date format (i.e. DD-MM-YY instead of MM-DD-YY)
If the time data in your log file is written in European (DD-MM-YY) format, check this box. FastStats Analyzer, by default, reads log files in United States (MM-DD-YY) date format. Note that this option only applies to IIS3 logs, which do not consistently write time data.Remove text before the first '.' in a domain name and ignore subdomains. Mach5 Analyzer, by default, removes all characters up to the first dot in a domain name. This makes all subdomains equivalent on your server, so that references to "www.mach5.com" show up the same as references to "mach5.com". If you need to track subdomains separately, you can turn off this option.
Do not look up hostnames for internal IP addresses. If you check this option, all references from IP addresses 10.* and 192.* will be omitted from analysis. These IP addresses are for internal network accesses only. This option only applies if your server is outside of your network.
FastStats Analyzer will, by default, try to figure outyour log file format automatically. Some web servers, however, produce logs that look exactly like standard formats in layout but actually put data in different places. If your server format is listed in this pulldown menu with an asterisk, then you may want to tell FastStats what kind of server you are running. Also, if FastStats incorrectly identifies your log format, you can force it to use a specific layout by choosing the format from the pulldown menu.
By choosing a default log format, new projects will by default have their log format set to your global options choice, but you can still override the log format option on a per project basis.
FastStats Analyzer will, by default, only display the 100 most requested items in a report, and the top 30 most requested items when exporting. You can adjust these numbers to show more or less information.
It is common for the time data in your log files to be recorded in an inappropriate time zone. To correct this, FastStats Analyzer allows you to add or subtract an offset to the hour recorded in the log file. This problem is common if a thirty party hosts your web site; the third partys servers may be located on the opposite side of the country, and in a completely different time zone. You can adjust the offset to any value between -12 and 12. The best way to determine the offset for your log files is to examine the times recorded near the beginning of your log file. If you know what time your web-hosting provider generates the log files, then you can just subtract to determine the offset. It may take some experimentation. Note that some servers record their log files in GMT time (which is 5-8 hours off times in the continental US).