Walter Vannini wrote:
> example: given a 28-day long log, I can do DAILY to know what happens on
> a given, say, Monday. It's the DAILY (as opposed to FULLDAILY) report. Fine
> Now I can also know what happens on the average 9-to-1Oam hour, it's the
> HOURLY report (as opposed to FULLHOURLY)
> *But*, I can't go any smaller than that. Why? Analog clearly knows how to
> collapse a longer time period in congruence classes (sorry, my translation
> of math italian) onto a given set (days, 24 hours), adding things up.
So what you're really getting at is that you want a "QUARTERLY" and "FIVELY" report
in addition to (or instead of) the current "(FULL)QUARTER" and "(FULL)FIVE" reports.
This makes sense to me. In fact I would find that much more useful that the current
ones. I've yet to find someone who really want to know the activity in five-minute
intervals for the last 3 days. But knowing your average daily usage in five-minue
intervals could be quite useful (for that matter why not take the limit and offer a
continuous usage chart for a given interval? e.g. AVGDAY gives you the average usage
over 24-hours).
So what you are suggesting is to use FROM and TO, with approriate scripting, to
generate n-minute interval files which are then cross-analysed to produce a n-minute
average report. This should be feasable, since you're only reporting on the number
of requeset (or page requests or bytes) for given time intervals, so you don't have
to worry about data loss. But the script might get a little hairy. :)
--
Jeremy Wadsack
Wadsack-Allen Digital Group
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
