SAWMILLFORUM

Thanks,

Randy

If some of the webserver log settings are "not checked", try setting up to log all fields from your webserver IIS manager control panel. Sometimes as a result of the pared down information (subset of fields reporting) Sawmill's parsing algorithms do not capture the field information as you would expect without having all fields in the log file. Sawmill will allow you to customize the fields you want to save in your database & report so having more vs. less information is good.

If you find that Sawmill is still not auto-detecting the log format you can send the log file to support@flowerfire.com (preferably < 3 MBs) and we can take a look at the format. It's possible there's a bug in our log format plug-in or if this is a variant of IIS that we currently do not support we can certainly add support for it. Typically adding support for a particular log format takes 2-3 weeks contingent upon support loads and complexity, however we also offer a pay for priority service if you need this format sooner assuming that it requires new development work to support the format.

I would venture to guess that the IIS log you are processing is something we currently handle (check 7.0.10g), and hopefully enabling all logging options in your IIS control panel will allow Sawmill to work seamlessly with the log data.

First lines in the W3SVC1 log file:
#Software: Microsoft Internet Information Services 5.0
#Version: 1.0
#Date: 2005-02-08 05:00:03
#Fields: date time c-ip cs-username s-ip s-port cs-method cs-uri-stem cs-uri-query sc-status cs(User-Agent) cs(Referer)
2005

First lines in the W3SVC3 log file:
#Software: Microsoft Internet Information Services 5.0
#Version: 1.0
#Date: 2005-02-08 05:55:47
#Fields: date time c-ip cs-username s-ip s-port cs-method cs-uri-stem cs-uri-query sc-status cs(User-Agent)

Other than the referer what's the difference and why does one log have so many more entires in it?

I've also upgraded to Sawmill 7.010 and still can't get session information. I see references to sessions in one of the cfg files but it doesn't seem to catch what it needs in our logss. I am only learning Sawmill so if my questions are basic, I apologize. I'm going to send a sample of each log that have been generated since turning on all IIS logging options.

Thanks,

Randy