ServerStat 2.1.6

Release Notes

This is a maintenance release to fix all known and reported problems.

A bug when processing Common Log Format logs didn't read the date correctly.

This is also the first release where the source code is available for download.

ServerStat 2.1.5

Release Notes

There was a reported problem with the Log file button with ServerStat 2.1.4. This and all known problems were fixed in this release.

ServerStat 2.1.4

Release Notes

ServerStat 2.1.3 made an attempt to support Quid Pro Quo's date format. In doing so, a math error caused the dates for WebSTAR's logs to report as all the same. This version fixes all known problems.

ServerStat 2.1.3

Release Notes:

ServerStat 2.1.1 has a problem processing Common Log Format logs. This was corrected with 2.1.3.

There was an error in the documentation for the FILTER command. To speed up the processing of the line, ServerStat resolves : into / earlier in the process. So, when creating a Filter command you should use /'s instead of :'s like you used to. This will require an update to the Settings files to process correctly.

New with 2.1.3 is limited support for Microsoft IIS, NT Extended Log Format. Windows NT has an option to produce logs with Extended Log Format tokens. They are space delimited rather than tab delimited so in order to support them in ServerStat a new line format needed to be defined. ServerStat can process these logs using LogType NT-Extended.

Quid Pro Quo Server is also now supported in a limited fashion. If Quid Pro Quo's log is set similar to the WebSTAR format and you add a !!LOG_FORMAT line with the equivalent WebSTAR token names, these logs can be processed. Quid Pro Quo's DATE token uses a Year 2000 date format different from WebSTAR's so a probe of the DATE field was needed in order to see if the date was MM/DD/YYYY whereas WebSTAR's date field uses MM/DD/YY when using /'s to delimit and -'s when using the 4-digit year. These logs can now be processed.

With the new log formats, testing was done on reading and processing the logs, but functions like ReWrite, Resolve were not. They may work, but support for reading the formats was requested. If you notice problems in this area, report them to support@kitchen-sink.com and we will try and resolve them.

ServerStat 2.1.1

Release notes:

There were a few items picked up with the first users of ServerStat 2.1. We have corrected all known bugs in this release. They are detailed below:

  1. [HOST_BOTTOM] command was misspelled in the code as [HOST_BOTOTOM] and would result in the [HOST_BOTTOM] report keyword being written directly in the report instead of its data.
  2. The RESULT token was not properly being parsed. If SC-STATUS or CS-STATUS were not available in the log, the 3 conditions OK, PRIV, ERR! were random. The result would be items not showing up in the [ARCHIVE] tokens. The data would be counted in the other sections of the report.
  3. Low memory situations: Under certain conditions, subroutines would ask to allocate memory and the application would run out of memory and crash. We take careful precautions when expanding the various statistic lookup areas where the memory manager routines are called, but not in every subroutine. The solve this a 64K buffer is left by all of the memory manager routines which should allow normal subroutines to get the memory they need without crashing the application. As always, it is best not to run out of memory but I think we will catch the majority of low memory situations now.
  4. When using [tables] command, there was a missing <TR> in the HTML when writing the [REFERER] tags which would result in the tables appearing as one long row if it displayed at all.
  5. The Personalization dialog box was removed since copying the program is now encouraged.

If you have errors to report, send them to:

support@kitchen-sink.com