Re: [Devmon] optional oid

[Richard F. <gol...@gm...>]

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.

On Wed, Jun 22, 2011 at 00:39, Johan Sjöberg
<Joh...@de...> wrote:
> I have only been able to solve this by creating separate templates for the different devices. But maybe there is a better way.
>
>> -----Original Message-----
>> From: Stef Coene [mailto:ste...@do...]
>> I want to monitor some Brocade fiber channel switches.  Some of them have
>> high avaible CP's.  So only some of them have the corresponding oids.
>>
>> If I add the oid to the message file, the switches who don't have this oid are
>> reporting this ('Missing repeater data for CPLastEvent for status msg') and no
>> update is send to xymon.