Re: afs_fsmon ext-script

["Tracy J. Di Marco White" <gendalia (at) iastate.edu>]

In message <Pine.LNX.4.64.0811130823530.4753 (at) titan.desy.de>, Martin Flemming writes:
}
}Hi, Tracy et all ...

Hi Martin!

}Nice that you are on the list again,
}dosen't you disappear from it for one or two years ....
}
}So i take another chance to ask you,
}for your configuration of the various graphs of your afs_fsmon-script ...

It is the most useless graph ever. I should break it out into multiple
RRDs, but then I don't know how to display them.
[afs}
        TITLE AFS fileservers calls waiting for thread
        YAXIS calls waiting for thread
        DEF:callswaiting=afs.rrd:callswaiting:AVERAGE
        DEF:freePackets=afs.rrd:freepackets:AVERAGE
        DEF:threadsidle=afs.rrd:threadsidle:AVERAGE
        DEF:serverConnections=afs.rrd:serverconnections:AVERAGE
        DEF:clientConnections=afs.rrd:clientconnections:AVERAGE
        DEF:peerStructs=afs.rrd:peerstructs:AVERAGE
        DEF:callStructs=afs.rrd:callstructs:AVERAGE
        DEF:freeCall=afs.rrd:freecalls:AVERAGE
        DEF:calls=afs.rrd:calls:AVERAGE
        DEF:allocs=afs.rrd:allocs:AVERAGE
        DEF:readdata=afs.rrd:readdata:AVERAGE
        DEF:readack=afs.rrd:readack:AVERAGE
        DEF:readdup=afs.rrd:readdup:AVERAGE
        DEF:readspurious=afs.rrd:readspurious:AVERAGE
        DEF:readbusy=afs.rrd:readbusy:AVERAGE
        DEF:readabort=afs.rrd:readabort:AVERAGE
        DEF:readackall=afs.rrd:readackall:AVERAGE
        DEF:readchallenge=afs.rrd:readchallenge:AVERAGE
        DEF:readresponse=afs.rrd:readresponse:AVERAGE
        DEF:sentdata=afs.rrd:sentdata:AVERAGE
        DEF:sentresent=afs.rrd:sentresent:AVERAGE
        DEF:sentack=afs.rrd:sentack:AVERAGE
        DEF:sentbusy=afs.rrd:sentbusy:AVERAGE
        DEF:sentabort=afs.rrd:sentabort:AVERAGE
        DEF:sentackall=afs.rrd:sentackall:AVERAGE
        DEF:sentchallenge=afs.rrd:sentchallenge:AVERAGE
        DEF:sentresponse=afs.rrd:sentresponse:AVERAGE
        LINE2:callswaiting#000000:Calls waiting
        LINE2:freePackets#0000FF:Free Packets
        LINE2:threadsidle#008000:Idle Threads
        LINE2:serverConnections#0080FF:Server connections
        LINE2:clientConnections#00FF00:Client connections
        LINE2:peerStructs#00FFFF:Peer Structs
        LINE2:callStructs#800000:Call Structs
        LINE2:freeCall#8000FF:Free Calls
        LINE2:calls#8080FF:Calls
        LINE2:allocs#80FF00:All Locs
        LINE2:readdata#80FFFF:Read Data
        LINE2:readack#FF0000:Read Ack
        LINE2:readdup#FF00FF:Read Duplicates
        LINE2:readspurious#FF8000:Read Spurious
        LINE2:readbusy#808000:Read Busy
        LINE2:readabort#8080FF:Read Abort
        LINE2:readackall#80FF00:Read Ack All
        LINE2:readchallenge#80FFFF:Read Challenge 
        LINE2:readresponse#FF0000:Read Response 
        LINE2:sentdata#80FFFF:Sent Data
        LINE2:sentresent#FF00FF:Read Resent 
        LINE2:sentack#FF0060:Sent Ack
        LINE2:sentbusy#FF8090:Sent Busy
        LINE2:sentabort#8030FF:Sent Abort
        LINE2:sentackall#802F00:Sent Ack All
        LINE2:sentchallenge#83eFFF:Sent Challenge 
        LINE2:sentresponse#eeee00:Sent Response 

}> It was also simple to have all the numbers rxstats generates fed into an
}> rrd, so pretty graphs are available, although calls waiting for a thread is
}> the only one monitored
}
}Unfortunatley not for me, :-(

So I don't have the correct answer, just an answer.  I'd accept better
answers if anyone finds one.

Tracy J. Di Marco White
Information Technology Services
Iowa State University