Shawn

I'm not using SPLITNCV as I wanted a bit more flexibility in the format of the status report (I wanted to have comment line, single colons not delimiting values etc.), but am using an external script. You may find my earlier reply here http://www.hswn.dk/hobbiton/2008/10/msg00159.html useful though.

With the external script mechanism you don't need to restart Hobbit if your test generates additional indexes, only if you add new tests. I'm not entirely sure whether SPLITNCV works the same although it looks OK - but you sound perfectly at home with the source, so have a look at that (do_ncv.c). If you're interested, I attach my parsing script to the end of this - enter the test name list and change the regex for your needs. The commented lines were from when I was using a single RRD file for all indices, but that doesn't give the flexibility of displaying multiple graphs, or adding additional indices.

Graham Nayler

#!/usr/bin/python

import sys, re

def main(): #print len(sys.argv), sys.argv if( sys.argv[2] in (<enter test name list here>)): #print "%s scanning file '%s'"%(sys.argv[2], sys.argv[3]) data = "" lineno = 0 f = open(sys.argv[3],'r') for line in f: lineno = lineno+1 if (lineno > 2): mo = re.match("(.*\s+)?([^\s]+)\s*::\s*(-?[0-9\.]*).*$",line) if not (mo == None): if( len(mo.group(3)) > 0 ): print "DS:%s:GAUGE:600:U:U"%mo.group(2)

if len(data) > 0:

data = data + ":" + mo.group(3)

else:

data = mo.group(3)

                    print "%s.%s.rrd"%(sys.argv[2],mo.group(2))
                    print mo.group(3)
    f.close()

if( len(data) > 0 ):

print "%s.rrd"%sys.argv[2]

print data

if __name__ == "__main__": main()

----- Original Message ----- From: "Shawn Heisey" <hobbit at elyograg.org> To: <hobbit at hswn.dk> Sent: Monday, October 13, 2008 9:56 PM Subject: Re: [hobbit] wildcards or regex with SPLITNCV

Shawn Heisey wrote:

...

I am working on setting up graphs to track an application. I have created a test that produces the output at the end of this message, I want to use SPLITNCV to handle it, but I don't want to be required to update the hobbit configuration and restart when the number of indexes in the system increases. I have not been able to find a SPLITNCV example like the following one for regular NCV:

http://www.hswn.dk/~henrik/howtograph.txt

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

Shawn,

Sorry, I obviously overinterpreted your earlier posts about patching and getting your snapshot working.

I can't really comment about your application, other than to say I think you'll have a major problem getting different numbers of traces on different graphs within a single test. Running multiple tests, with some having individual traces/graph and some having multiple, is probably the only way you'll be able to manage that.

But back to your SPLITNCV problem, I finally had a bit of a closer look at it, as it's so closely related to what I've been doing myself. Yes it will allow adding datasources within a test without restarting hobbit (or more accurately, and seriously, having to delete and reinitialise the RRD files, so losing previous history). Don't know about it's support in 4.2, but it is supported in 4.3 - but it is broken.

Here's my reply to someone else today on the subject, which describes the usage and the fix http://www.hswn.dk/hobbiton/2008/10/msg00423.html

Regarding the python script, essentially it skips the first two header lines, then parses any lines it sees of the format <any old junk> {space} <datasource_name> {space} :: <signed floating point value> <more junk>

and writes for each line found the following three lines to stdout DS:<datasource_name>:GAUGE:600:U:U <testname>.<datasource_name>.rrd <value>

As it receives each <value> the script host (hobbitd_rrd) updates (or generates if required) the named RRD file.

Subsequently, I've now changed it to output a DS line equivalent to what the SPLITNCV mechanism does DS:lambda:GAUGE:600:U:U partly as I had some very long datasource names, and RRD throws an error (and fails to create the file) if it sees datasources longer than 19 characters.

FYI, as I see it, the overheads of using external script mechanism additional to the SPLITNCV methods are: one process fork per test report write the body of the test report to a temporary diskfile run the script delete the temporary diskfile

Graham Nayler

----- Original Message ----- From: "Shawn Heisey" <elyograg at elyograg.org> To: <hobbit at hswn.dk>; <apalmer at mainstreamdata.com> Sent: Monday, October 20, 2008 7:38 PM Subject: Re: [hobbit] wildcards or regex with SPLITNCV

{snip}

I finally got around to looking at this. I think I'm even more confused. Not sure where you got the idea I'm comfortable with the source ... I've looked at the 4.3 sources trying to get rid of warnings and get it working, but the only thing that did was remind me just how many years it's been since I did any C programming. My eyes glazed over a bit with your python too, I haven't invested any time in that language yet.

{snip}