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 +------------------------------------------------------------------------
