Upgraded: snmpdiskio 0.9.6 (Disk I/O statistics on Linux)

[gandalf]

There seems to be an error with the XML file, as no OID that should be queried for the index is shown
Reinhard

[plouj]

I am stuck at step 3. "USAGE" of the installation process.
After adding the "Disk - I/O (bytes/sec)" graph template to my host template, I still cannot add this same template to an already existing device. I just don't see the option in the "Add Graph Template:" drop down menu.

I even added the appropriate data queries to my device already, but still cannot see the option for adding a graph. I would like to figure out how to add the graph through the device editing page rather than adding a 'disconnected' graph to the tree and then associating it with the device later. As far as I know, all the previous installation steps were completed successfully, especially the template XML file importation.

[plouj]

Well, it looks like I don't actually need to add the Graph Template to my existing host. My device I/O is being monitored and graphed just fine now.

[driden91]

I have the same problem .
i follow the README instruction to setup it.
And that's the debug mode of the graph management
[code][ RRDTool Command:

/usr/bin/rrdtool graph - \
--imgformat=PNG \
--start=-108000 \
--end=-300 \
--title="poste_perso-2 - Disk I/O (bytes/sec) - sda1" \
--rigid \
--base=1000 \
--height=120 \
--width=500 \
--alt-autoscale-max \
--lower-limit=0 \
--vertical-label="bytes per second" \
--slope-mode \
DEF:a="/home/www/cacti/rra/poste_perso2_io_read_164.rrd":io_read:AVERAGE \
DEF:b="/home/www/cacti/rra/poste_perso2_io_read_164.rrd":io_write:AVERAGE \
AREA:a#4668E4:"Read" \
GPRINT:a:AVERAGE:" Average\:%8.2lf %s" \
GPRINT:a:MIN:"Min\:%8.2lf %s" \
GPRINT:a:MAX:"Max\:%8.2lf %s" \
GPRINT:a:LAST:"Current\:%8.2lf %s\n" \
AREA:b#EAAF00:"Write":STACK \
GPRINT:b:AVERAGE:"Average\:%8.2lf %s" \
GPRINT:b:MIN:"Min\:%8.2lf %s" \
GPRINT:b:MAX:"Max\:%8.2lf %s" \
GPRINT:b:LAST:"Current\:%8.2lf %s\n"

RRDTool Says:

ERROR: opening '/home/www/cacti/rra/poste_perso2_io_read_164.rrd': No such file or directory
/code]


what is the solution please ?

[cspenpen]

Hi

when I select the partitions you want graphs created for and click Create.

then show this error messages

[gandalf]

[case_h99]

I use Centos 4.4 (kernel 2.6)

I sucessfully installed the last version of the script and the template

I monitor a server whit no much traffic... btw I think only syslog is using disk.
In fact if I use iostat, I can see this:

[gandalf]

Sorry, it is not _my_ script. So I can't answer your question as I do not use it on my own
Reinhard

[mavericque]

Hi all,
snmpdiskio is a great extension to cacti! I have used it on a couple of systems. But I can't get it to work on net-snmp 5.4 and kernel 2.6.18.2. I figured out that the exec clause is deprecated, so I use the extend clause in snmpd.conf:

[jeffreymlewis]

First I'd like to say thanks so much for posting your scripts and graph templates. They are most useful!

A few weeks ago I discovered that the I/O stats I'm graphing are not accurate. I think I've discovered the problem.

The 'snmpdiskio' script seems to be grabbing the wrong fields on Redhat 3. The 'hdInBlocks' function is grabbing $10 which is the 'wmerge' field according to the header in /proc/partitions. The 'hdOutBlocks' function is grabbing $8 which is 'ruse' on Redhat 3.

[mmuse]

The "Custom Data [Template: ucd/net - Device I/O]" is asking for the following info:
Index Type
Index Value
Output Type ID

What should I enter for each?

[jspilon]

has anyone manage to get the Data query to resolve partitions to mount points ?

[jspilon]

Hello,

First off, thanks for this template. I am planning to aggregate all my partitions' data into one graph, but I see that the drive has less i/o than all the partitions added together... (sum of sda* = sda isn't true) any idea why ???

[ravton]

The patch below gets this to work on CentOS, Redhat and likely other 2.6 kernels. Fixed is wrong fields. Tested with RAID, LVM, and partitions - the data all lines up correctly now amongst all them!

Enjoy and thanks to the original author!


38c38
< $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $10 !~ /[0-9]+/ { printf "%.0f\n", $7 * 512 } ' $PROCFILE
---
> $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $10 !~ /[0-9]+/ { printf "%.0f\n", $5 * 512 } ' $PROCFILE
43,44c43,44
< awk ' $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 ~ /[0-9]+/ { printf "%.0f\n", $6 * 512 }
< $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 !~ /[0-9]+/ { printf "%.0f\n", $5 * 512 } ' $PROCFILE
---
> awk ' $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 ~ /[0-9]+/ { printf "%.0f\n", $8 * 512 }
> $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 !~ /[0-9]+/ { printf "%.0f\n", $7 * 512 } ' $PROCFILE

[pdestefanis]

This makes sense. According to what I've found for 2.6 kernels in http://developer.osdl.org/dev/robustmutexes/src/fusyn.hg/Documentation/iostats.txt, the fields from /proc/diskstats are fixed by the patch in the previous post.

For partitions:

Field 1 -- # of reads issued
This is the total number of reads issued to this partition.
Field 2 -- # of sectors read
This is the total number of sectors requested to be read from this
partition.
Field 3 -- # of writes issued
This is the total number of writes issued to this partition.
Field 4 -- # of sectors written
This is the total number of sectors requested to be written to
this partition.

For drives:

Field 1 -- # of reads issued
This is the total number of reads completed successfully.
Field 2 -- # of reads merged, field 6 -- # of writes merged
Reads and writes which are adjacent to each other may be merged for
efficiency. Thus two 4K reads may become one 8K read before it is
ultimately handed to the disk, and so it will be counted (and queued)
as only one I/O. This field lets you know how often this was done.
Field 3 -- # of sectors read
This is the total number of sectors read successfully.
Field 4 -- # of milliseconds spent reading
This is the total number of milliseconds spent by all reads (as
measured from __make_request() to end_that_request_last()).
Field 5 -- # of writes completed
This is the total number of writes completed successfully.
Field 7 -- # of sectors written
This is the total number of sectors written successfully.
Field 8 -- # of milliseconds spent writing
This is the total number of milliseconds spent by all writes (as
measured from __make_request() to end_that_request_last()).
Field 9 -- # of I/Os currently in progress
The only field that should go to zero. Incremented as requests are
given to appropriate request_queue_t and decremented as they finish.
Field 10 -- # of milliseconds spent doing I/Os
This field is increases so long as field 9 is nonzero.
Field 11 -- weighted # of milliseconds spent doing I/Os
This field is incremented at each I/O start, I/O completion, I/O
merge, or read of these stats by the number of I/Os in progress
(field 9) times the number of milliseconds spent doing I/O since the
last update of this field. This can provide an easy measure of both
I/O completion time and the backlog that may be accumulating.

The only thing I don't like is the fixed sector size (512), but I can't find a place where the sector size is specified. I know, it's fairly standard anyway.

Cheers,

Pablo