> > I'm obviously very curious as to what pages are taking over 5 seconds to > process, when this was occurring, and whether this was a particular > visitor that was affected or a more general problem. So I've been trying > to get more detail on this element. I've been messing with things like > the FLOOR commands, but so far all I've got is either more of the same, or > the command ignored completely. Am I asking too much of Analog or have I > just not found the right command combination to use yet. > > > > You are looking for a command which only looks at lines with long > processing times, but analog happens not to have such a command. But > in any case, when you get to this level of detail, you really need to > look in the raw logfiles at the offending lines and see if you can see > a pattern.
If you are running on Unix (or have Unix commands available) you could probably use sed or something to parse out the lines in the file where the processing time is greater than 5 seconds and then use Analog to do further analysis. You can hijack Analog's UNCOMPRESS command to do this. It performs any inline command on files content before it's processed as long as the command's output goes to stdout. Thanks, Jeremy Wadsack Seven Simple Machines +------------------------------------------------------------------------ | 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 +------------------------------------------------------------------------
