From: Cook, G. <GW...@ma...> - 2004-08-13 15:49:31
|
Ben Clewett wrote: > Garry, Yves, >=20 > To address the two problems Yves found: >=20 > 1. Range values for Warn and Crit not supported. > 2. Only store the last found value for Max and Min. >=20 > I propose a new data structure for the Binary data which will also > increase the speed of the queries and lower the size of the > data files. [snip]=20 > --------------------------------------------------- >=20 > Alternatively, we can hack the existing binary table. But > it's a mess > already. Biting the bullet one more time before version 1.0.0 might > make all the difference....=20 >=20 > Regards, Ben. I won't pretend to understand all of that, but I think I grok enough of it. It sounds like a good plan to me. Most of the time I don't think we will see a range for WARN/CRIT, although it is important to treat it properly when we do. I also feel that most of the time MIN/MAX will be NULL, but also needs to be treated properly. The MIN/MAX will be used to scale the graphs, correct? If so, you'll only need to figure out a CRIT-based formula for autoscale when MIN/MAX is NULL. Unless of course UOM=3D'%', in which case MIN/MAX may be omitted by = plugin developers and should be assumed - 0/100. Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.308.6228 (Office) - 720.220.1862 (Mobile) |