Splitncv and analysis.cfg 🔗 link

Hi All,

I have set up a test to monitor the queue depth on several queues on an MQ
server and the output on the xymon page looks like so -

*Queue Count

TSG.DRE.AA.CUST  - prd.CustomerQueue           : 130
TSG.DRE.AA.ORDE  - prd.OrdersQueue             : 0
TSG.DRE.AA.PAYM  - prd.PaymentsQueue           : 0*

I've configured xymon to collect the data in seperate
RRDs for graphing using splitncv method.

The RRDs have names like below -

QueueCount,TSG_DRE_AA_CUST_prd_CustomerQueue.rrd

The name of the check being performed i.e the column in Xymon is - QueueCount

Now, what I want is for the QueueCount column to go red
 once the queues reach a certain threshold. So in my analysis.cfg file
I placed the below entry.


HOST=PROD_MQ
        DS QueueCount
SysopPerfCount,QueueCount,TSG_DRE_AA_CUST_prd_CustomerQueue.rrd:lambda

100 COLOR=red "TEXT=Backlogs on MQ"

Somehow this never works and the status never changes to red no matter what
is the queue count on the queues. The data collection to the RRD and the
graphs work fine. Any idea what is going wrong here. Any fundamental thing
I am missing before trying to change status of checks based on RRDs using
splitncv.

Thanks!

Regards,
Raunak

It all looks OK to me.  I do this sort of thing also, and I don't think
I've configured things differently to you.

Some things to try:

1. Check the output of "rrdtool info".  In particular, confirm that the DS
name is "lambda" and its type is "GAUGE".  There should be only one DS name.

2. Run "xymoncmd xymond_client --dump-config" and make sure that this
parsed and normalised config looks like you think it should look.

3. Run in xymonlaunch, add "--debug" to xymond_client and see if the
logfile shows anything interesting.

4. Confirm that the file SysopPerfCount,QueueCount,TSG_
DRE_AA_CUST_prd_CustomerQueue.rrd exists. Instead of typing it out, try
cutting and pasting from your analysis.cfg, to detect problems with typos
or hidden characters.

J

On 23 July 2015 at 12:21, Raunak Kothari <user-a8a393f86145@xymon.invalid> wrote: