>>:Analog processes log file lines in a stream, sequentially. As each >>:line is encountered it's checked against the data filters to determine >>:if it will be included and then the data is added to the hashes that >>:hold the results for the reports. (This is simplified of course.) So >>:there is no place where Analog really could write out a log file of >>:the lines that are just in the Request Report. In fact the cache files >>:are fairly close to a serialized version of a memory dump just before >>:reports are written.
>>[DF] this gets to the heart of my question. Could the log line not >>therefore be written out at the point at which it is determined it will >>be included? > This seems a little distant from Analog's stated purpose. Agreed. Also, the original questions was for Analog to write out all the lines that corresponded to entries in the Request Report. Perhaps that's just different interpretations of the same thing, but the lines that are filtered with the date-level *INCLUDE/EXCLUDE commands also include lines that end up in the Redirected Requests Report, Failed Requests Report, etc. And, of course, the Request Report is also filtered by REQINCLUDE/REQEXCLUDE which is applied to the lines in the reports AFTER all log file lines have been processed (i.e. to the data that's similar to the cache files). However, I also recognize the advantage of only having to manage configurations in a single place (your Analog configuration files) and the value of not having to run multiple passes through the log files. One "solution" (probably not optimal) is to use grep/perl to pre-process all the log files Analog reads, rather than filter them with any of HOSTINCLUDE/HOSTEXCLUDE, FILEINCLUDE/FILEEXCLUDE, BROWINCLUDE/BROWEXCLUDE, REFINCLUDE/REFEXCLUDE, USERINCLUDE/USEREXCLUDE, VHOSTINCLUDE/VHOSTEXCLUDE, or STATUSINCLUDE/STATUSEXCLUDE in your Analog configurations. As a trick/hack, you can actually use the UNCOMPRESS command to trigger any pre-processor on any file types. So if you did have a script called "filter-logfiles" you could do something like "UNCOMPRESS filter-logifles *". Of course, this means you can't have any other UNCOMPRESS commands, but with the latest 5.91beta1 you probably won't need any anymore. -- Jeremy Wadsack Wadsack-Allen Digital Group +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
