The problem with using this style of template is that we assume that there are only the 4 sensors on any given device that we model and that the OIDs always match the to the same sensors (.1.2.0 -> Comms LH, .2.2.0 -> Comms RH, .3.2.0 -> Serv LH, .4.2.0 -> Serv RH).
While this may be acceptable in this situation, i.e: the above assumption is correct, for something like disks you can't predict how many/what type there will be in a system and the data collector script automatically determines this when the host is modeled. So if the above assumption is false, i.e: there may be a different number of sensors depending on the device or the sensors map to the OIDs differently from device to device, then creating a custom data collector would be the better solution. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=21714#21714 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
