[Xymon] combine status and data in same column with graph

[Asif Iqbal]

On Wed, Nov 13, 2013 at 7:41 PM, Vernon Everett <everett.vernon at gmail.com>wrote:

> Hi Asif
>
> Have a look here.
> https://wiki.xymonton.org/doku.php/monitors:db_cpu.ksh
> This is an example of what I think you are trying to do.
>
>
Looking at your link. What is  db-cpu::100 means in GRAPHS ? I did not see
any thing in xymonserver.cfg man page to explain the ``:100'' after the
columnname

So essentially you are taking advantage of both status and data channel in
the same script like I started with.

I will revisit my initial approach, except I will make sure there is no NCV
like data, like Jeremy suggested,  when sending to status channel or it
screw up the rrd with garbage.

Thanks for the link.


Regards
> Vernon
>
>
> On 14 November 2013 08:39, Jeremy Laidman <jlaidman at rebel-it.com.au>wrote:
>
>> On 14 November 2013 03:52, Asif Iqbal <vadud3 at gmail.com> wrote:
>>
>>>  You might find that adjusting the TEST2RRD variable to include only
>>>> "columname" and not "columnname=ncv" might do the trick.  The man page for
>>>> xymond_rrd talks about the "ncv" part only being used for status messages.
>>>>  But this is a long-shot.
>>>>
>>>
>>> Looks like if I do not have  columnname=ncv it does not generate a rrd
>>> file.
>>>
>>
>> :-(
>>
>>
>>> I did some clean up so nothing in MSG has NCV like data and I added the
>>> NCV data in the <-- ... --> . It did create the rrd file with the correct
>>> NCV keys, but values
>>> are zeros. It is dropping the values for some reason? So I am almost
>>> there if I can figure out why the values are not showing up.
>>>
>>
>> Are the values you're reporting counter-type (that is, always
>> incrementing) or gauge-type?  If you're sending gauge data and it's being
>> treated as counter data, then you will often get mostly zeroes or NaN.  By
>> default, NCV data is expected to be DERIVE which is a type of counter.  If
>> you want to change to GAUGE, then you need to set NCV_columnname to
>> describe this:
>>
>> NCV_columnname="foo:GAUGE,bar:GAUGE"
>>
>> The other option would be using --extra-test and --extra-script and parse
>>> the values from the status channel to generate rrd?
>>>
>>
>> Perhaps.  These seem a lot trickier to use.
>>
>> One thought I had about this was to setup "--extra-test" and
>> "--extra-script" on the status channel, to filter out the status messages
>> from xymond_rrd.  If you use "--extra-script=/bin/true" and
>> "--extra-test=columnname" then I think it will feed the data to "/bin/true"
>> instead of parsing it itself.  Of course "/bin/true" will produce no
>> output, and hence no data.
>>
>>
>>>   I want the graph show up in the test page, so sending it to just
>>> trends won't work, right?
>>>
>>
>> Right.  It needs to be listed in TEST2RRD to show up in the test page.
>>
>> Hmm, just noticed this in the doco:
>>
>> "No graph on the status page, but OK on the trends page
>> Make sure you have *ncv* listed in the GRAPHS setting in
>> xymonserver.cfg. (Don't ask why - just take my word that it must be there).
>> "
>>
>> Do you have "ncv" listed in GRAPHS?
>>
>> J
>>
>>
>> _______________________________________________
>> Xymon mailing list
>> Xymon at xymon.com
>> http://lists.xymon.com/mailman/listinfo/xymon
>>
>>
>
>
> --
> "Accept the challenges so that you can feel the exhilaration of victory"
> - General George Patton
>



-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20131114/42feab07/attachment.html>