Jun 17, 2008 10:09 AM
Q for devs - Broken functionality or incorrect forum post??
-
Like (0)
"HaydnH" wrote:
Thinking about it, I think that method would be wrong anyway as /dev/sda is listed in the snmpwalk as well as /dev/sda1,2 etc so we'd get the same IO shown multiple times for each parition. Perhaps there is a better way of doing this now anyway? e.g: creating a datasource for /dev/sda & /dev/sdb on the same graph, and a third data point for /dev/sda + /dev/sdb?
"HaydnH" wrote:
Hi Beanfield,
Yes, you have understood me correctly - from what you have said I believe this functionality is broken. I can only put in a data source for a specific partition, any OID that has children fails, Using `zenperfsnmp run` to debug:
1.3.6.1.4.1.2021.13.15.1.1.5.18:
Works fine and gives diskIOReads values for /dev/sda1 in this case
1.3.6.1.4.1.2021.13.15.1.1.5:
Prints a "oid 1.3.6.1.4.1.2021.13.15.1.1.5 is bad" message from `zenperfsnmp run`
If we can confirm that Zenoss should (used to?) accept SNMP tables as data sources (instead of single value OIDs) and someone else can confirm that this is broken, let me know and I'll raise a ticket.
"HaydnH" wrote:
OK, that does work... please would you send that method to those responsible for the documentation as it's not exactly straight forward for those not so familiar with Zenoss?
I think the fact that the template name must be "HardDisk" is why I was failing - it's things like this that really get on my nerves with Zenoss, it seems like it's going to be a great product - it's just a little unrefined at present!
Thank you beanfield for all your help!
MIB Module:
UCD-DISKIO-MIB .1.3.6.1.4.1.2021.13.15
diskIOTable .1.3.6.1.4.1.2021.13.15.1
diskIOEntry .1.3.6.1.4.1.2021.13.15.1.1
diskIOIndex .1.3.6.1.4.1.2021.13.15.1.1.1 Integer32 Range: 0-65535
diskIODevice .1.3.6.1.4.1.2021.13.15.1.1.2 Text Size: 0-255
diskIONRead .1.3.6.1.4.1.2021.13.15.1.1.3 Counter
diskIONWritten .1.3.6.1.4.1.2021.13.15.1.1.4 Counter
diskIOReads .1.3.6.1.4.1.2021.13.15.1.1.5 Counter
diskIOWrites .1.3.6.1.4.1.2021.13.15.1.1.6 Counter
diskIOLA1 .1.3.6.1.4.1.2021.13.15.1.1.9 Integer32 Range: 0-100
diskIOLA5 .1.3.6.1.4.1.2021.13.15.1.1.10 Integer32 Range: 0-100
diskIOLA15 .1.3.6.1.4.1.2021.13.15.1.1.11 Integer32 Range: 0-100
diskIONReadX .1.3.6.1.4.1.2021.13.15.1.1.12 Counter64
diskIONWrittenX .1.3.6.1.4.1.2021.13.15.1.1.13 Counter64
Data Points: Types
COUNTER Saves the rate of change of the value over a step period.
DERIVE Same as COUNTER, but it allows negative values as well.
ABSOLUTE Saves the rate of change, but assumes that the previous value is set to 0.
GAUGE Saves only the actual value itself. There are no divisions or calculations.
"zmg" wrote:
This should probably be converted into a community zenpack.
UCD-DISKIO-MIB::diskIONRead.17 = Counter32: 3603906560
UCD-DISKIO-MIB::diskIONRead.18 = Counter32: 18904064
UCD-DISKIO-MIB::diskIONRead.19 = Counter32: 273843712
UCD-DISKIO-MIB::diskIONRead.20 = Counter32: 699032576
UCD-DISKIO-MIB::diskIONRead.21 = Counter32: 4096
UCD-DISKIO-MIB::diskIONRead.22 = Counter32: 184418304
UCD-DISKIO-MIB::diskIONRead.23 = Counter32: 869376
UCD-DISKIO-MIB::diskIONRead.24 = Counter32: 1497600
UCD-DISKIO-MIB::diskIONRead.25 = Counter32: 2425037824
I have this working but it only shows sda and sdb, what I am looking
for is sda1, sda2, sda3, etc. IO for each partition, can this do it?
What I have is this.
UCD-DISKIO-MIB::diskIONRead.17 = Counter32: 3603906560
UCD-DISKIO-MIB::diskIONRead.18 = Counter32: 18904064
UCD-DISKIO-MIB::diskIONRead.19 = Counter32: 273843712
UCD-DISKIO-MIB::diskIONRead.20 = Counter32: 699032576
UCD-DISKIO-MIB::diskIONRead.21 = Counter32: 4096
UCD-DISKIO-MIB::diskIONRead.22 = Counter32: 184418304
UCD-DISKIO-MIB::diskIONRead.23 = Counter32: 869376
UCD-DISKIO-MIB::diskIONRead.24 = Counter32: 1497600
UCD-DISKIO-MIB::diskIONRead.25 = Counter32: 2425037824
My OID is .1.3.6.1.4.1.2021.13.15.1.1.3
But it only maps .1.3.6.1.4.1.2021.13.15.1.1.3.17 which is sda, the .
18, .19 are each slice
beanfield :
Is this still the current best-practice for getting per-device diskIO graphs from Net-SNMP's diskIOTable ?
I added zenoss.snmp.UCDHardDiskMap to my ModelerPlugins but my graphs under hard disk are showing 'no data'
Not a problem, we can just use a custom template instead?
But I'm not sure how your instructions are supposed to work with Table Index magic.
AFAIK, if I add a single numeric OID to a template, it will graph it.
But in your example, you're listing an OID of a tree branch.
How is the graph supposed to know how to handle this?
Is it supposed to Draw a graph for each disk in an SNMP walk operation (minus those in the regex?)
-------------
Here's a picture of my SNMP data points being configured per your instruction
And here's the resulting graphs, showing NAN/Zero values, as I suspect:
Message was edited by: Brian Seklecki
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||