To expand on this some and provide ultimate flexibility how about an optional NCV configuration file? When used, this file could be ordered by TEST, with HOSTs being qualified, and appropriate pattern matching of course (sort of the opposite of hobbit-alerts.cfg). Each entry under the test would contain the text to look for (it could be different for a test/host pair) and the graphing parameters for that specific combination. I would envision:
TEST=pg_util Page_Utilization,GAUGE,0:100 TEST=sp_util Spool_Utilization,GAUGE,0:100 HOST=vm1 Queue_File,GAUGE,0:100 Data_File,GAUGE,0:100 HOST=^vse.* GRAPH=pqueue
Where the pg_util graph will look for the text 'Page_Utilization' and graph the white space delimited value after it (after = or :). And sp_util will look for Spool_Utilization for vm1 and graph that data. The graphing parameters will come from hobbitgraph.cfg (as usual), with the default being the test name. For hosts beginning with 'vse' it will look for two values, Queue_File and Data_File and use the pqueue graphing parameters. Strange, but true, I have a column that has a different number of data points with different names depending upon the host (they are both considered spool utilization).
I certainly don't know all of the variations, but this may eliminate the need for most extra tests.
Henrik Stoerner wrote:
On Fri, Nov 11, 2005 at 09:57:31PM -0600, Dan Vande More wrote:
Ok, I found the issue.
Though I've written dozens of bb clients, I've never come across exactly how BB expects the information. This might be hobbit specific
It is a result of how the NCV handler in hobbitd_rrd expects data to be formatted, so yes - this is hobbit specific.
however. In my original email, I stated I was sending the data from my script like:
home/monitor/bb/bin/bb 1.2.3.4 "status iron1-mgmt.Memoryutil green Memoryutil : 11"
This is not the correct way to do this hobbit-wise. You need to put a \n in between the color status and the data you're pushing via ncv.
I've updated the hobbitd_rrd man page and added this to the section on how to use the NCV data:
Note that each "NAME : value" must be on a line by itself. If you have a custom script generating the status- or data-message that is fed into the NCV handler, make sure it inserts a newline before each of the data-items you want to track.
That should hopefully make it clearer - I'm sorry it bit you.
Perhaps it's just my interpretation, but I think we should reword the documentation to explicitly say we do not need to do any --extra-script or --extra-tests if one is using ncv.
Agreed - did that as well.
Finally, I perused a lot of the man pages and code for the past few hours, and only found one error - and that was a spelling error. In ~hobbit/server/etc/hobbitgraph.cfg, temperature is misspelled:
comment out the [tempeature] section above, and
Fixed :-)
I'm now using ncv for collecting 8 datapoints and it appears to collect and graph data flawlessly. Thanks for the solid implementation Henrik.
Thank you for reporting what you found - that is the kind of feedback I need to make Hobbit better.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006