I have had quite a bit of success in accomplishing everything I wanted using a (somewhat) modified "Analog Run" VBScript (http://christopherlewis.com/analog_run.vbs.htm by Christopher Lewis) and only requiring the weeks log files plus cache files for other days, plus a main analog.cfg and a .cfg for each site. Thanks to C.Lewis, I even get Report Magic Output for those that need the pretty graphs :)
If anyone really wants it, I can spend the time better documenting what I did. AP -----Original Message----- From: AP [mailto:[EMAIL PROTECTED] Sent: Thursday, February 24, 2005 4:21 PM To: [email protected] Subject: [analog-help] Multiple Websites? I have to generate reports for multiple web sites. After considering writing my own scripts to run analog, I searched for other solutions and began using the "Analog Run" VBScript (http://christopherlewis.com/analog_run.vbs.htm) by Christopher Lewis. Since I have multiple sites, I'm currently using two versions of the script for each site--one runs the daily report and creates a cachefile, the other uses the cachefile and creates the weekly, monthly, and YTD reports. I use analog.cfg for common settings and each site has a cfg file for the daily reports and a cfg file for the other reports. So I wind up with four "configuration/script" files for each site. Not so bad I thought, even though I would have preferred to have fewer . . . and then I realized that the reports generated using the cachefiles are not quite accurate, because when using cachefiles, Analog has no idea of what timeframe the cache files are for. So now I'm having to consider another set of cfg files and VBScript files for the weekly, monthly and YTD reports, and I'll have to figure a way to limit which cache files each of those needs to read . . . That's the point at which I wondered whether I might be reinventing the wheel! So, does anyone use Analog for multiple websites to generate similar reports? Do you have any advice, thoughts, comments, best practices, etc. that you could share? Btw, I need to use cache files because each of the sites has multiple servers and as the year progresses, the quantity and size of the (uncompressed) log files moves past the terabyte mark. I've tried pointing Analog at compressed files but it takes too long to even analyze a week! (Not analog so much as the uncompression!) Thanks! AP -----Original Message----- From: Aengus [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 7:01 AM To: Support for analog web log analyzer Subject: Re: [analog-help] Multiple Websites? On Thursday, February 24, 2005 9:20 PM [GMT], Other <[EMAIL PROTECTED]> wrote: > That's the point at which I wondered whether I might be reinventing > the wheel! So, does anyone use Analog for multiple websites to > generate similar reports? Do you have any advice, thoughts, > comments, best practices, etc. that you could share? >From your description of the situation, you actually have two different problems - one is the set of reports that you want for a single website, giving the wrinkles that cachefiles throw up, and the other problem is doing this for multiple sites. It sounds like some of the difficulty you are experiencing might be caused by trying to solve both problems at once. Once you have it working for a specific case to your satisfaction, getting it working for the general case should be more straightforward. For example, rather than using lot's of different config files, it may be that you only need to change one or two parameters in a config file, in which case it may simply be more efficient to have a single, common config file, and call Analog with the additional parameters as command line arguments instead. > Btw, I need to use cache files because each of the sites has multiple > servers and as the year progresses, the quantity and size of the > (uncompressed) log files moves past the terabyte mark. I've tried > pointing Analog at compressed files but it takes too long to even > analyze a week! (Not analog so much as the uncompression!) That shouldn't normally be the case. In fact in some situations, Analog can actually be faster with compressed logfiles, because the I/O overhead is lower. Aengus +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
