Graph definitions

Hi Phil

Have you, or anybody else on the list, got an example of such a script?

Thanks
    Vernon

-----Original Message-----
From: Phil Wild [mailto:user-e365c1418192@xymon.invalid]
Sent: Thursday, 30 October 2008 4:43 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Graph definitions

Hi Vernon,

You need to write your own backend data collector and have hobbit pass the data to it through a change in hobbitlaunch. You parse the data yourself at the server side and then build a single rrd file for every entry. You then use the FNPATTERN as you have already specified...

From memory, I think this is lightly covered in the man pages.

Cheers

Phil

2008/10/27 Everett, Vernon <user-9da1a1882f49@xymon.invalid>:

Hi all

Is there any way to define a graph definition for values that may or
may not be available.

Let's work with CPU temperature, just as an example.

In hobbitserver.cfg, I can define this NCV_systemp="*:GAUGE"
(And the other ncv definitions)
It then generates rrd files for all the servers.

However, some systems have 1 cpu, some have 2, and some 4.
So the rrd files only have entries for the number of CPUs.

In the hobbitgraph.cfg we can define the graph, with 4 cpu
temperatures, but if the rrd file doesn't contain 4 fields (i.e.
system has only 2 CPUs), it doesn't generate a graph.
It is also not possible to have a separate graph definition for 1, 2
and 4 CPU systems.

The other way round it, is to have each CPU in a separate file, and
define FNPATTERN= with a wildcard.
But how do we get the ncv module to put each field in a sepreate rrd file?

Regards
     Vernon


NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or copyright material.
You must not read, copy, use or disclose them without authorisation.
If you are not an intended recipient, please contact us at once by
return email and then delete both messages and all attachments.

--
Tel: XXXX XXX XXX
Fax: XXXX XXX XXX
email: user-e365c1418192@xymon.invalid


NOTICE: This email and any attachments are confidential. 
They may contain legally privileged information or 
copyright material. You must not read, copy, use or 
disclose them without authorisation. If you are not an 
intended recipient, please contact us at once by return 
email and then delete both messages and all attachments.