It would be far simpler to use different static definitions per device subclass. To do that, all you have to do is look at the admin guide regarding templates, and create your own templates, using an SNMP datasource in which you specify the OID and then a graph definition.
It's rather simple once you read up on it a little. Creating autopicked templates is something I have no idea how to do. -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University rjnichol wrote, On 4/13/2009 1:07 PM: > Hello, > > I have some devices that I am trying to add additional support for in my new > install of Zenoss (first install, first time user). I'm trying to add > support to let me do performance monitoring for the SNMP evnvironmental > sensor table available on the device. > >>From what I've been reading, I "think" what I need to do is add a new device >>component class? (similar to IpInterface)? This does not appear to be >>trivial and I can't seem to find any documentation to help me. > > Here's an EDITED snippet from the sensorTable, but it varies among the Occam > device models. > > # snmpbulkwalk -v2c -cxxxxxx 10.x.y.z .1.3.6.1.4.1.6066.2.1.3.2.1.1.1.1 > OCCAM-SENSOR-MIB::sensorName.3 = STRING: +5V > OCCAM-SENSOR-MIB::sensorName.15 = STRING: External temperature > OCCAM-SENSOR-MIB::sensorName.20 = STRING: Fan1 > > OCCAM-SENSOR-MIB::sensorType.3 = INTEGER: volts(2) > OCCAM-SENSOR-MIB::sensorType.15 = INTEGER: celsius(3) > OCCAM-SENSOR-MIB::sensorType.20 = INTEGER: rpm(4) > > OCCAM-SENSOR-MIB::sensorValue.3 = INTEGER: 496 > OCCAM-SENSOR-MIB::sensorValue.15 = INTEGER: 37 > OCCAM-SENSOR-MIB::sensorValue.20 = INTEGER: 5340 > > OCCAM-SENSOR-MIB::sensorScale.3 = INTEGER: centi(3) > OCCAM-SENSOR-MIB::sensorScale.15 = INTEGER: units(4) > OCCAM-SENSOR-MIB::sensorScale.20 = INTEGER: units(4) > > OCCAM-SENSOR-MIB::sensorTimeStamp.3 = Timeticks: (180094642) 20 days, > 20:15:46.42 > OCCAM-SENSOR-MIB::sensorTimeStamp.15 = Timeticks: (180094852) 20 days, > 20:15:48.52 > OCCAM-SENSOR-MIB::sensorTimeStamp.20 = Timeticks: (180094868) 20 days, > 20:15:48.68 > > > > Can anyone point me in the right direction to support this? I can entertain > the idea of using different 'static' definitions per device model if that > would be more simple. > > Thanks! > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=33352#33352 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
