I am running DNN3 using a shared SQL server (database is size restricted). My site log was set to store in my database, but I have a huge amount of traffic and it was filling to quickly (30 days), causing me problems by exceeding my database size limits. SO I changed the site log to use file system (just a click of my mouse, simple right?) on my dedicated Windows 2003 server and now my site log does not work. I can not afford to store my site log in database.

Sorry for my ignorance, but does the site log only work when stored in database? Am I stuck now not having a site log?

My Host Settings
Site Log Storage: File System
Site Log Buffer (Items): 1
Site Log History (Days): 45

My Host Scheduler

DotNetNuke.Services.Log.SiteLog.PurgeSiteLog, DOTNETNUKE

Every 1 Day

Every 2 Hours

5/26/2005 2:24:30 M

Thank you
Mike
Florida USA

Yeah - I would like to understand this better my self.  I haven't had much luck researching it.

 

the file based storage is designed to be parsed by offline statistics tools such as webtrends, and won't work with the builtin sitelog, as it only uses the database at the moment. Whatever tool you use, you'll still have to create a filter to parse it correctly. It was created as many users have substantial filesystem storage, but only limited database storage. If you have access to the IIS logs, I'd recommend parsing them (I use awstats.sourceforge.net for my sites). A disadvantage of this approach, is that no tools that I know of integrate back to the database to provide the page names, though this limitation is reduced if you're using friendlyurls.

Cathal

Thanks for the info Cathal

excuse me for kicking this thread, but I am wondering if someone could post his awstats .conf file, because i'll receive an error when I parse the logfiles. Awstats.pl says the LogFormat is incorrect, I changed the default value to 2; same error. I changed it using the parameters -> same error.

Afaik there is no option in DNN for changing the logged variables?

You'll have to create your own custom log format, as the one's awstats ship with are all the common webserver formats, and we store data in a propietary format i.e. objSiteLogs.AddSiteLog(PortalSettings.PortalId, objUserInfo.UserID, URLReferrer, Request.Url.ToString(), Request.UserAgent, Request.UserHostAddress, Request.UserHostName, PortalSettings.ActiveTab.TabID, AffiliateId, intSiteLogBuffer, strSiteLogStorage) [note:this doesn't support optional changes) . Theres some notes in the awstats.conf file, and @ http://awstats.sourceforge.net/docs/awstats_faq.html#LOGFORMAT on how to create custom logfile formats.

Realistically, if you're using awstats, you're probably better pointing it at the raw IIS logs.

Cathal

This is the format produced by dotnetnuke:

date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status

is there an option to add referrer and filesize, because i can't find any LogFormat option in awstats.{portalname}.conf to work with this output, even the samples provided in this file: http://awstats.sourceforge.net/docs/awstats_faq.html#PERSONALIZEDLOG wouldn't work