But I want it to collect the same variable twice (or to be efficient collect it once but use it twice...) - for instance I want to have a summary set of graphs at the device level showing key statistics (EG Traffic on key interfaces), but then at the interface level I want to see the detailed information (Eg Traffic, error counts etc).
I am sure there are many instances where it would be legitimate to want to use the same OID value more than once, but few enough that collecting it each time would be acceptable... I have dug around enough in the zenperfsnmp script to know that the issue is due to the fact that the oidmap collection is indexed by the oid itself rather than by (say) the rrd path which would be unique. However I don't know Python so am not sure of the impact of changing that index value would have within the data collection routines where it seems to disappear into the complexities of callbacks and self generating/modifying code (Which is what I guess 'chain' does!). The fact that this impacts at multiple levels within the device is a pain (eg you need to know what is collected at interface level when you are trying to work at device level) & changing an interface collection could break - multiple - device collections.... Is this a bug or a PEP ? I favour the former as it is not a documented restriction...! -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=19986#19986 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
