wildcards or regex with SPLITNCV

Shawn Heisey hobbit at elyograg.org
Mon Oct 13 21:48:41 CEST 2008


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.

Is there a way to define the SPLITNCV_testname variable in such a way 
that it can handle this?  Also, I want to be able to set up the 
live_count and broker_count variables as counters, but be able to track 
negative changes as well as positive.  I'm not sure if the DERIVE format 
mentioned in the docs will do negative changes.  Normally, the value 
marches ever higher, but when there are problems, it will go down, and I 
want to see that on the graph.  The _time variables and the rest of the 
_count variables will be gauges.

Is this something that can be accomplished?  If I have to set up all the 
graphs as gauge and deal with an ever-increasing value for the special 
entries, then I will do that.

This is on the production system, running version 4.2. I started with 
the source package from the debian backports archive, then patched with 
the central BBWin patch and the allinone patch in addition to the 
existing debian-specific patches.  I had to resolve a couple of 
conflicts, but got it to compile and run.

Script output:
==============
live_count : 30635889
diff_count : 0
broker_time : 1355
broker_count : 30635889
rss_time : 4525
rss_count : 1680777
indy1s2_time : 863
indy1s2_count : 53532
indy1s3_time : 34
indy1s3_count : 789
indy2s1_time : 23
indy2s1_count : 674006
indy2s2_time : 25
indy2s2_count : 952450
indy3s1_time : 21
indy3s1_count : 1004714
indy4s1_time : 32
indy4s1_count : 997684
indy4s2_time : 32
indy4s2_count : 996035
indy5s1_time : 27
indy5s1_count : 1000602
indy5s2_time : 77
indy5s2_count : 999003
indy6s1_time : 26
indy6s1_count : 1003493
indy6s2_time : 25
indy6s2_count : 1001920
indy7s1_time : 28
indy7s1_count : 999484
indy7s2_time : 26
indy7s2_count : 1003172
indy8s1_time : 25
indy8s1_count : 1004038
indy8s2_time : 24
indy8s2_count : 1000058
indy9s1_time : 25
indy9s1_count : 999745
indy9s2_time : 24
indy9s2_count : 998908
indy10s1_time : 28
indy10s1_count : 995340
indy10s2_time : 25
indy10s2_count : 1001914
indy11s1_time : 21
indy11s1_count : 998153
indy11s2_time : 20
indy11s2_count : 1000448
indy12s1_time : 21
indy12s1_count : 995504
indy12s2_time : 22
indy12s2_count : 996100
indy13s1_time : 26
indy13s1_count : 997570
indy13s2_time : 50
indy13s2_count : 999154
indy14s1_time : 22
indy14s1_count : 997059
indy14s2_time : 21
indy14s2_count : 995457
indy15s1_time : 27
indy15s1_count : 1003780
indy15s2_time : 25
indy15s2_count : 997950
indy16s1_time : 66
indy16s1_count : 999673
indy16s2_time : 34
indy16s2_count : 994129
indy17s1_time : 28
indy17s1_count : 998302
indy17s2_time : 56
indy17s2_count : 975723




More information about the Xymon mailing list