Hi !
I've got a mysterious problem, because there are too many graph-links (dead links) on the trend-page for my SPLITNCV-Graphs ..
... see http://desy.de/~flemming/afss3.png (The first afss3-graph is right and pretty but follows of ghostly links)
Im running [xymon01] /usr/lib/xymon/server/bin # ./xymongen --version xymongen version 4.3.4
but this problem was already there with older versions :-(
I startet with a normal NVC-method and there was everything ok
i've got one afss.rrd and could show every of my 20 value in a seperate graph on the trend-page ... but now i want to use the SPLITNCV-Method to have for each value one seperate rrd, so i can compare each value for several servers .. this also works but unfortunaltey ony with these addittional ghostly/dead links :-(
Has somebody an idea what's going wrong ?
thanks & Cheers
martin
Hi !
Please give me a little advice ....
Does nobody got an idea ?
.. or do you more details ?
thanks in advance
martin
On Fri, 7 Oct 2011, Martin Flemming wrote:
Hi !
I've got a mysterious problem, because there are too many graph-links (dead links) on the trend-page for my SPLITNCV-Graphs ..
... see http://desy.de/~flemming/afss3.png (The first afss3-graph is right and pretty but follows of ghostly links)
Im running [xymon01] /usr/lib/xymon/server/bin # ./xymongen --version xymongen version 4.3.4
but this problem was already there with older versions :-(
I startet with a normal NVC-method and there was everything ok
i've got one afss.rrd and could show every of my 20 value in a seperate graph on the trend-page ... but now i want to use the SPLITNCV-Method to have for each value one seperate rrd, so i can compare each value for several servers .. this also works but unfortunaltey ony with these addittional ghostly/dead links :-(
Has somebody an idea what's going wrong ?
thanks & Cheers
martin
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
On 07-10-2011 22:43, Martin Flemming wrote:
I've got a mysterious problem, because there are too many graph-links (dead links) on the trend-page for my SPLITNCV-Graphs ..
... see http://desy.de/~flemming/afss3.png (The first afss3-graph is right and pretty but follows of ghostly links)
It has always been a bit tricky getting Xymon's svchost.cgi tool to figure out how many graph links it should include on the status page, simply because svchost doesn't know about how graphs map to RRD files (that knowledge lies in showgraph).
The best thing You can do is to include the line
<!-- linecount=N -->
in the status-message that your custom check sends to Xymon, with "N" being the correct number of graphs. That overrides the (flawed) heuristic that is currently being used.
Regards, Henrik
On Mon, 10 Oct 2011, Henrik Størner wrote:
On 07-10-2011 22:43, Martin Flemming wrote:
I've got a mysterious problem, because there are too many graph-links (dead links) on the trend-page for my SPLITNCV-Graphs ..
... see http://desy.de/~flemming/afss3.png (The first afss3-graph is right and pretty but follows of ghostly links)
It has always been a bit tricky getting Xymon's svchost.cgi tool to figure out how many graph links it should include on the status page, simply because svchost doesn't know about how graphs map to RRD files (that knowledge lies in showgraph).
The best thing You can do is to include the line
<!-- linecount=N -->
in the status-message that your custom check sends to Xymon, with "N" being the correct number of graphs. That overrides the (flawed) heuristic that is currently being used.
Thanks, Henrik for response :-)
Unfortunatley my attempts are not successfull V
Could you give me an advice where/how i should added it :I
that's my last lines of the perl-script :
Format output
$DATE = scalar(localtime(time));
$LINE="status $ENV{MACHINE}.$TEST $COLOR $DATE\n\n\n$rxdebug_status\n\n$afs_fs_status";
Send to BBDISPlay
system("$ENV{BB} $ENV{BBDISP} \"$LINE\""); exit;
thanks in advance
Martin
On Tue, Oct 11, 2011 at 8:11 PM, Martin Flemming <martin.flemming at desy.de> wrote:
that's my last lines of the perl-script :
Format output
$DATE = scalar(localtime(time));
$LINE="status $ENV{MACHINE}.$TEST $COLOR $DATE\n\n\n$rxdebug_status\n\n$afs_fs_status";
Maybe add this:
$LINE="$LINE <!-- linecount=20 -->"
Cheers Jeremy
participants (3)
-
henrik@hswn.dk
-
jlaidman@rebel-it.com.au
-
martin.flemming@desy.de