trying to figure out how to do this.. but is there a better way?
Scenario: <li>Log Files are deleted after 2 weeks so need a way to store them for analysis <li>Web host puts the .log files in a "secure" folder only accessible by password. <li>Would it be easier to scrap the history then write own stats?
Here's what I have so far but I'm getting a script timeout so I know it must be wrong..
excuse this code I'm really trying to figure this out :)
Dim sBasePath, sFileName, fs sBasePath ="ftp://[user]:[password]@[sitename].co.uk/Logs/" sFileName = "[filename].log"
Set fs = CreateObject("Scripting.FileSystemObject") on error resume next set objLogFile = fs.OpenTextFile(sBasePath & sFileName) if Err.Source <> "" then bErrFlag = 1 sErrDescription = "Invalid File name or Path. Please try again." set fs = Nothing end if
if bErrFlag = 0 then ' no file error set objTS = objLogFile.OpenAsTextStream(ForReading) response.write "is there a connection here?"
' clean up objTS.close set objTS = Nothing objLogFile.close set objLogFile = Nothing set fs = Nothing end if %>
Suzy, just an alternative suggestion here that might be worth considering - rather than relying on the log files themselves, why not take direct control of create the logging files yourself, particularly as you're using ASP anyway?
A technique I've used myself goes like this ..
(1) Each page to be logged looks at the ServerVariables collection to retrieve the required server variable values (typically you'd be interested in HTTP_REFERER, HTTP_USER_AGENT, REMOTE_ADDR, REMOTE_HOST, SERVER_SOFTWARE etc); (2) Append these values to your own xml file (with xml tags to map onto the required server variables); (3) Have your own asp admin-type page to read this xml file (i.e. the equivalent of trawling through the original log files) - here, you can use xsl to format the output how you want it. So you could have filter to allow you to parse the xml file and only show records for a specific HTTP_USER_AGENT or REMOTE_ADDR etc ..
I just see this sort of technique as giving you more control on the details being logged, with xsl transforms on your asp admin page giving you much greater control on you actually interrogate your own customised xml log files.