Feature Request: High- and low-water mark alarms

[Mel Beckman]

Here'a an idea that I think has been floated before. On a device 
interface, have two configurable values for each graphable 
measurement: a low-water traffic alarm and a high-water traffic 
alarm. MRTG 2.x has this feature, and it's wonderful. Sometimes you 
want to know when the traffic on a circuit falls below some expected 
value, and you almost always want to know when it goes above.

I'd recommend two thresholds for each alarm, a rising alarm threshold 
and a falling alarm threshold. Having different values for rising and 
falling helps eliminate oscillation-induced alarm floods. You get an 
alarm when traffic passes the rising threshold, but don't get an OK 
until it passes the falling threshold. You set these values far 
enough apart so that typical variations don't cross both thresholds.

Currently Intermapper logs events where traffic crosses 50% and 90%, 
but I think these won't ever generate actual alarms. And that's a 
good thing, because without rising- and falling-threshold triggers, 
Intermapper would put out a lot of oscillation-induced alarms.

I see this feature being implemented in the same way the "bandwidth" 
parameter is implemented today. There are default values (say, 0 and 
100%) that you configure by double-clicking in the Interface pop-up. 
Each value would have a rising and falling component, depicted with a 
/ seprarator, e.g.:

  Byte/Second: 27852 (222817 bps) low: 15/20% high: 80/70%

The threshold semantics for the low water mark have to be reversed: 
the first number is the falling threshold and the second is the 
rising threshold (e.g., alarm at 15% but don't OK until 20%).

 -mel

____________________________________________________________________
List archives: 
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]