"jbaird" wrote:

 

Yeah something like that.. sucks that it has to be executed on the remote system.. was hoping something along these lines was available via SNMP.

Thought i'd drop a note on this and hopefully get some others to help out w/ the graphing etc...

One method i've found for iostats collection is to leverage another communities efforts.

1. place the iostats.pl file attached into whatever directory

2. edit your snmpd.conf adding:
     pass .1.3.6.1.3.1 /usr/bin/perl /path/to/iostat.pl

3. create a /etc/cron.d/iostat with following content:
     * * * * * iostat -kxd 30 2 > /tmp/io.tmp && mv /tmp/io.tmp /tmp/iostat.cache

4. restart cron

5. snmpwalk -v2c -c<your_community> <host>:<port> .1.3.6.1.3.1

6. viola you have iostats for all devices via snmp.

7. leverage someone elses hardware in getting it added to your hardware tab or perf tab / device

ref: http://www.markround.com/archives/48-Linux-iostat-monitoring-with-Cacti.html

Would be great if we could figure out how to do some mappings similar to yaketystats in that it's able to desern what physical and logical devices are mapped to. ie your /dev/mpath or /dev/dm devices mapped to logical volume names etc..

Regards,

Message was edited by: guyverix

I will not kid you, the code is simplistic (I was just starting to learn bash scripting, and this was my first daemon) so the exec statement itself is defining the disk you want to get the stats on.  It is not a table return value per device.  It does however work very well to get what you are asking for.

Message was edited by: guyverix I will check and see how much of a PITA it would be for this to return a table value per device. 

As promised, here you go.

Create directory /opt/snmp-scripts

This must contain iostat-snmp and iostat-snmp-v2

chmod 755 both of the files, they will be retrieving the data from the logs.

copy iostatd and iostatdd into /etc/init.d/ and chmod them to 755 (also needs root ownership for the init.d dir)

copy snmpd.local.conf to /etc/snmp/

edit snmpd.local.conf to reflect your hard disks that you want to get values for.

Go into the rc#.d runlevel for the server and type:

ln -s ../init.d/iostatd S99iostatd (start it at boot)

type /etc/init.d/iostatd   (this calls iostatdd with no args,)

now type /etc/init.d/snmpd reload

Verification:

the files that are created are in /var/tmp/iostat-<x or t>

run a tail on them.  They are set to update every 10 seconds.  (this can be changed inside iostatdd itself)

now snmpwalk -v2c -c public localhost .1.3.6.1.4.1.8072.1.3.2

If everything is set up correctly, you will have your data.

Message was edited by: guyverix

Darn, almost forgot.  The init.d daemon is active for a Debian system currently.  If it complains at startup, comment out the Debian code, and uncomment the RH code that I have commented.  (or ask me to UL a RH version exclusive)

I would also recommend setting up a cron that restarts the daemon once a week/moth/whatever, since there is no log rotation, when the daemon is started it always wipes the previous file and goes again from scratch.  (why eat the disk space)

guyverix,

The only help i was really looking for is the graphing of the data in zenoss on say a 'custom' device tab.  I've found the example code for how to create a new zenpack which adds the additional tab.  I just haven't had the time to put it all together.  I did find your post helpful though on the ramdisk part.  I wouldn't expect it to be a high io process though, so not entirely certain it's needed in my implementation. Here are a few of the links.

Links:

message/36233#36233

message/40812#40812

Regards,

c0ns0le