no iostat rrds? 🔗 link

Hello,

my (solaris) clients report iostat-data for the disks in client section [iostatdisk]. However, no iostat-rrds are created. I've tried to change the data and headers to conform to larrd-iostat ([iostat] section), but still no rrds.
How can I get hobbit to cretae the iostat rrds?

regards,
Paul

PS: I'm using hobbit 4.2

anyone who has a solotion for this?

Paul

Paul van Eldijk schreef:

Henrik could give a better answer to this.
As far as I know there is no server code to handle iostatcpu or iostatdisk data.


Dominique
UNIL - University of Lausanne

Paul van Eldijk wrote:

Dominique Frise schreef:

True. but as far as I can tell there is code for iostat itself (do_iostat.c in src/.../hobbitd/rrd/). I've modified the client output to conform with the requered output (BEGINKEY..ENDKEY BEGINDATA..ENDDATA) and the client is reporting the data in the corrent format under [iostat]. But still no output. what an I missing here?

Paul

On Fri, Apr 11, 2008 at 09:22:51AM +0200, Paul van Eldijk wrote:

anyone who has a solotion for this?

Not really. The code in Hobbit for the iostat graphs was "ported"
from the original BB "larrd" tool, I haven't really used it myself.
Even when I was running larrd it was a bit flaky in doing graphs,
as I recall it.

Could you show me what the [iostatdisk] section looks like on your
clients?


Regards,
Henrik

Henrik Stoerner schreef:

The standard report from the clients looks like:
[iostatdisk]
extended device statistics
device,r/s,w/s,kr/s,kw/s,wait,actv,svc_t,%w,%b,
ssd0,a,0.1,0.9,0.3,1.3,0.0,0.0,17.8,0,0
ssd0,b,0.0,0.0,0.0,0.0,0.0,0.0,4.3,0,0
ssd0,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd0,d,0.1,0.4,2.1,8.2,0.0,0.0,15.0,0,0
ssd0,e,0.0,0.0,0.0,0.1,0.0,0.0,10.3,0,0
ssd0,f,0.3,0.2,24.6,29.3,0.0,0.0,11.2,0,0
ssd0,h,0.0,0.4,0.0,0.2,0.0,0.0,14.6,0,1
ssd3,a,0.1,0.9,0.3,1.3,0.0,0.0,18.0,0,0
ssd3,b,0.0,0.0,0.0,0.0,0.0,0.0,4.4,0,0
ssd3,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd3,d,0.1,0.4,2.0,8.2,0.0,0.0,15.1,0,0
ssd3,e,0.0,0.0,0.0,0.1,0.0,0.0,10.5,0,0
ssd3,f,0.2,0.2,22.7,24.2,0.0,0.0,12.0,0,0
ssd3,h,0.0,0.4,0.0,0.2,0.0,0.0,14.6,0,1
ssd6,a,3.3,2.5,72.2,23.4,0.0,0.0,6.7,0,3
ssd6,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd6,h,0.0,0.0,0.0,0.0,0.0,0.0,4.4,0,0
ssd7,a,3.1,2.6,72.1,23.7,0.0,0.0,6.7,0,3
ssd7,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd7,h,0.0,0.0,0.0,0.0,0.0,0.0,3.1,0,0
ssd8,a,3.4,2.3,72.2,21.5,0.0,0.0,6.1,0,2
ssd8,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd8,h,0.0,0.0,0.0,0.0,0.0,0.0,3.5,0,0
ssd9,a,3.2,2.5,72.1,23.3,0.0,0.0,6.5,0,2
ssd9,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd9,h,0.0,0.0,0.0,0.0,0.0,0.0,3.0,0,0
nfs1,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
extended device statistics
device,r/s,w/s,kr/s,kw/s,wait,actv,svc_t,%w,%b,
ssd0,a,0.0,0.8,0.1,0.9,0.0,0.0,17.9,0,0
ssd0,b,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd0,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd0,d,0.0,0.3,0.0,1.3,0.0,0.0,16.9,0,0
ssd0,e,0.0,0.0,0.0,0.0,0.0,0.0,9.8,0,0
ssd0,f,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd0,h,0.0,0.4,0.0,0.2,0.0,0.0,13.2,0,1
ssd3,a,0.0,0.8,0.1,0.9,0.0,0.0,17.9,0,0
ssd3,b,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd3,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd3,d,0.0,0.3,0.0,1.3,0.0,0.0,17.0,0,0
ssd3,e,0.0,0.0,0.0,0.0,0.0,0.0,10.0,0,0
ssd3,f,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd3,h,0.0,0.4,0.0,0.2,0.0,0.0,13.8,0,1
ssd6,a,0.0,0.8,0.0,4.1,0.0,0.0,8.2,0,1
ssd6,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd6,h,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd7,a,0.0,1.2,0.0,6.9,0.0,0.0,10.1,0,1
ssd7,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd7,h,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd8,a,0.0,1.4,0.1,9.1,0.0,0.0,12.3,0,1
ssd8,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd8,h,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd9,a,0.0,0.8,0.0,3.7,0.0,0.0,6.9,0,1
ssd9,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
ssd9,h,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
nfs1,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0


On one client I changed this to:
[iostat]
BEGINKEY
d0 /
d6 /var
d12 /staging
d20 /u01
d9 /home
ENDKEY
BEGINDATA
     r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b s/w h/w trn tot device
     0.0    2.2    0.2    2.9  0.0  0.1    4.4   27.8   1   1   0   0 0   0 d0
     0.0    0.3    0.0    1.5  0.0  0.0   12.2   21.1   0   0   0   0 0   0 d6
     0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0   0   0 0   0 d12
     0.0    4.5    0.2   25.9  0.0  0.0    0.0    8.2   0   3   0   0 0   0 d20
     0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0   0   0 0   0 d9
ENDDATA

to match the sample in the code for do_iostat.c

I also tried the latter with section header [iostatdisk], but none of the formats lead to any iostat rrds.
Also no logging of any error can be found. It looks like the rrd-daemon doesn't read it, some way or the other.

regards,
Paul

Regards,
Henrik

iostat graphs on Solaris in hobbit are broken.
http://www.hswn.dk/hobbiton/2007/07/msg00335.html

Even after these patches there seems to be a parsing issue on some filesystems.  ie. some filesystems get a solid graph line, some filesystems are a broken line.  "Random" data seems to be missing from the rrd's.  I have not located where the bug is yet though.

Craig Cook

iostat graphs on Solaris in hobbit are broken.
http://www.hswn.dk/hobbiton/2007/07/msg00335.html

Even after these patches there seems to be a parsing issue on some filesystems.  ie. some filesystems get a solid graph line, some filesystems are a broken line.  "Random" data seems to be missing from the rrd's.  I have not located where the bug is yet though.
 
Craig Cook

On Thu, May 1, 2008 at 8:15 PM,  <user-618593604956@xymon.invalid> wrote:

iostat graphs on Solaris in hobbit are broken.
http://www.hswn.dk/hobbiton/2007/07/msg00335.html

so can we enable iostat graph now ?

I see this in the client data for example

[iostatdisk]
extended device statistics
device,r/s,w/s,kr/s,kw/s,wait,actv,svc_t,%w,%b,
sd0,a,0.2,3.4,24.0,118.4,0.0,0.1,30.2,0,2
sd0,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
sd1,a,0.2,3.4,24.1,118.4,0.0,0.1,28.4,0,2
sd1,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
nfs3,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
nfs4,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
extended device statistics
device,r/s,w/s,kr/s,kw/s,wait,actv,svc_t,%w,%b,
sd0,a,0.0,3.2,1.1,99.2,0.0,0.1,26.8,0,2
sd0,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
sd1,a,0.0,3.2,0.6,99.2,0.0,0.1,23.9,0,1
sd1,c,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
nfs3,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0
nfs4,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0

I am interested in a iostatdisk graph.

Also my customer wants to be alerted for some of this issues on above iostat

- A service time value of more than 30ms on a disk that is more than 10% busy
- disk is more than 60% busy
- average wait time of more than 5

Also wants to be alerted for vmstat sr

- scan rate greater than 200 pages per second

-- 

Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

On Wed, Mar 11, 2009 at 2:19 PM, Asif Iqbal <user-6f4b51ac2a40@xymon.invalid> wrote:

still like to know if an extension script is the answer or can be
enabled as part of hobbit

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

On Thursday 12 March 2009, Asif Iqbal wrote:

I don't know if the iostat graphs are part or will be part of the core xymon 
code base, but I have an aix external script for it.  There was a request on 
this list to port it to linux:
http://www.docum.org/foswiki/bin/view/Xymon/LinuxIostatGraphs


Stef