Support for analog web log analyzer wrote: >>The correct approach would be for analog to loop round generating >>logfile names from FROM to TO ... >>It doesn't seem difficult, but I haven't a pressing enough need to put >>the time in myself - for me it's more of a gotcha than a real problem. > > > If Analog has to loop around generating logfiles names from the From and To, > why doesn't it just do the analysis while it's at it? > > Oh, yeah - it does! > > Analog analyses log files. If you need logfile management, it's not > immediately obvious that it needs to be built in to Analog.
Logfile management is necessarily part of the webserver. But having generated daily/weekly/monthly logfiles, how do you efficiently report on an arbitrary period ? Eg - I have monthly archives for some websites, and daily for others. My regular monthly report works fine. To get my regular weekly report I always read the whole month to date, and use a shell script to add in last month too if necessary, letting analog discard the rest of the data. If I want to report occasionally on a larger interval, I have to create a special config file. Currently, the choices seem to be: 1. specify a super-set of the necessary logfiles, and let analog discard what it doesn't need. 2. accept one or more reports based on several subsets. 3. handcraft your config to read the right logfiles. Analog's pretty fast, so maybe (1) is acceptable - takes about .6s per day read. (2) isn't really acceptable. (3) can be done with a perl wrapper, shell script, or something to insert the right LOGFILE statements based on FROM & TO, but my perl's not up to the general case. Analog does a great job of allowing from & to dates to be specified, so that they don't have to be handcrafted, but something else seems to be required to have it read the right logfiles. Maybe I've missed a trick, but while it's easy to specify the LOGFILE template to analog as a parameterised date, and easy to specify the from and to dates, there's an additional, awkward, step, which analog doesn't do, which is making sure the right logfiles get read for those dates - it just does the TO date. If I wrap analog in something else to do it, I've got to do all the date parameterisation, and analog's own parameterisation doesn't get used. Analog's a great tool, and I like its reports, but I don't have a neat solution to this issue - my script to fiddle the week report seems ugly, and fiddling, say, a quarterly report would be worse. The only place for a neat solution seems to be inside analog, which understands the from & to, and the logfile name template, and could, with the addition of a loop, read the exact 7 daily logs required for a weekly report, and 90 days or 3 months for a quarterly report. As I say - maybe I've missed something - if so, please tell me ... Best Regards Chris Any views expressed in this message are those of the sender and not necessarily those of CCA Group. The unauthorized use, disclosure, copying or alteration of this message is forbidden. The contents of this message may be confidential and/or privileged, copyright CCA Group and are intended solely for the use of the individual or entity to whom they are addressed. Whilst this message has been scanned, CCA Group cannot guarantee that it is virus free or compatible with your systems and accepts no responsibility for any loss or damage arising from its use. The recipient is advised to run their own anti-virus software. If you receive this message in error please contact [EMAIL PROTECTED] immediately, destroy any copies and delete it from your computer systems. +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------
