This is actually a pretty difficult one in terms of being able to address
gracefully for all cases. As you've surmised, the DS part stands for 'Data
Source', specifically in the command creation definition syntax of a data
source file used by rrdtool.
The traceback is being caused by the rrdtoolmodule.so binary.
It appears that the best one can hope for without a lot of effort is to
trace things back from the OID.
The really crude solution is to add the following into zenperfsnmp.py, int
the storeRRD() function, just after the line that says "min, max =
oidData.minmax":
=== 2 lines beneath here to save in the file ======
Code:
self.log.info( "Saving OID %s data in %s: value= %s, type=%s, min=%s,
max=%s, createcommand=%s" % \
( oidData.path, value, oidData.dataStorageType, min, max,
oidData.rrdCreateCommand ) )
======
Python *is* sensitive to spaces, so it needs to be lined up to other lines in
that function.
This will generate *LOTS* of entries, and is definitely only suited for
debugging purposes, and ideally only a test box. This won't affect any data
collection or anything, but it will add a significant amount of load.
Make a backup copy of your Products/ZenRRD/zenperfsnmp.py file before you
touch anything, too. :)
kells
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=27058#27058
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
