T.R | Title | User | Personal Name | Date | Lines |
---|
2601.1 | Duration != periodicity | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Fri Mar 20 1992 12:02 | 7 |
| Have you tried specifying the duration which you would like used by
PA to compute the statistics? Alarms does not know, in general, what
duration you prefer, so if no duration is specified, PA uses its default.
(That is, you might want a rule evaluated once an hour, but to reduce
polling prefer that the statistic is computed for a duration of 5 minutes).
|
2601.2 | Not sure if the 'schedule time' is passed to PA | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Fri Mar 20 1992 13:19 | 31 |
| RE: .0
> If I specify an alarm with an interval of 30 minutes ( at every 00:30:00 ),
> why don't we use this time as the default polling interval automatically.
> This would make alarming on statistics more simple and valueable, because
> with a duration of less than 30 minutes I loose information.
Karl,
I like it! 8)
But (didn't you know it) -- I'm not sure if the 'Schedule time' is actually
passed to PA. Without going into the details; Time is broken up into
two pieces: Schedule Time and Scope-of-Interest Time.
The 'at every 00:30:00' is the schedule time. The IM/Dispatcher will
coordinate calling PA every 30 minutes. I believe (but not sure) that
this Schedule portion of the time-specification is lost (ie, PA doesn't
get to see it).
The 'for duration 00:30:00' is the scope-of-interest time. PA does see
this (and the IM/Dispatcher ignores it). PA uses this value to determine
when to collect the data used in its calculations.
------
I'm sure this isn't the answer you wanted to hear. Time is very complex
and could use some help. Your suggestion is a good idea and could help
make Time much simpler.
/keith
|
2601.3 | duration | MFRNW1::SCHUSTER | Karl Schuster @MFR Network Services | Mon Mar 23 1992 04:10 | 3 |
| re .1
I specify: at every 00:30:00, for start -0:00:00 duration 0:25:00
But I loose the counters of the last 5 minutes.
|