|
From: Buchan M. <bg...@st...> - 2011-06-23 14:34:53
|
On Thursday, 23 June 2011 05:35:19 Richard Finegold wrote: > An alternative to separate templates is separate columns. You could > dedicate a column to CPs (e.g "cp" or "ha"), then use something like > DEVMON:tests(diag,if_load,if_stat) to avoid including your additional > test. > > I use this technique for two of my hosts (Dell PowerEdge) that don't > have RAIDs (they use "tests(fans,power,temp)"). > > IMO, it usually is better for alerts/history/graphs to have more > granularity, particularly if they can fail independently or not > uniformly supported. I personally feel it was bad judgement for the > APC templates to combine temperature and humidity (which have > different units) into one "env" column, when other devices (e.g. Cisco > 6509, Dell PowerEdge, Compaq server) have a distinct "temp" column. > But maybe I'd feel differently if I had at least one humidity sensor > somewhere, or had a non-APC device with an env column. Other environmental sensors (I need to check if these are in svn ...) have separate tests for everything (air, audio, dew, door, dry, enclosure, error, humidity, motion, other, temp). Of course, then there are others which have crap MIBs, and bundle everything into one table and populate only some of the "rows" depending on what sensors are connected. Regards, Buchan |