From Wim.Nelis@nlr.nl Wed Jun 24 08:21:23 2026 From: Wim.Nelis@nlr.nl To: xymon@xymon.com Subject: [Xymon] List of graphs of a devmon test is too long Date: Thu, 23 Feb 2012 11:36:03 +0100 Message-ID: <4F461693.3060802@nlr.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3439879485067003788==" --===============3439879485067003788== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, we are using xymon 4.3.7 and devmon 0.3.1-beta1, r233. Some of the=20 devmon tests on interfaces of switches and routers use the rrd collector=20 of xymon. Those tests contain thus both a table and additionally one=20 graph per interface. However, for *each* test using the devmon rrd=20 collector there are three additional pointers to non-existing graphs.=20 The number of additional non-existing graphs is thus independent of the=20 number of interfaces being monitored. The following is the page source of a test to check for packet drops on=20 3 interfaces of a router:

Thu 2012.02.23 10:58:22


Interface discards:
Input  discard load alert thresholds: yellow=3D5.0%, red=3D10.0%
Output discard load alert thresholds: yellow=3D5.0%, red=3D10.0%

 ...  ...  ...  ...  ... 


If namePacket rate in



eth010.55


eth118.05



eth20.00


wlan04.37






Note:=20
Discard rate: Number of discards per second
Discard load: Number of discards per packet


Devmon version 0.3.1-beta1-r233 running on sodn164u


Status unchanged= in 6 days,21 hours, 2 minutes
Status message received from 137.17.28.26
The (very) long lines have been truncated, at the "...", to enhance the=20 readability. In subdirectory ~xymon/data/rrd/nlrcve02-lan there are 3=20 RRDs, not 6. How xymon does determine the linecount, 6 in the example above, is not=20 clear to me. However, it is the number of lines in the HTML comment=20 section containing the RRD data, which is always 3 more than the number=20 of interfaces. How can I configure xymon in such a way that the number of graphs=20 matches the number of interfaces? Kind regards, Wim Nelis. *****************************************************************************= ************************************* The NLR disclaimer is valid for NLR e-mail messages. This message is only meant for providing information. Nothing in this e-mail = message amounts to a contractual or legal commitment on the part of the sender. This message may contain information that is not intended for you. If you are= not the addressee or if this message was sent to you by mistake, you are requested to inform the sender an= d delete the message. Sender accepts no liability for damage of any kind resulting from the risks i= nherent in the electronic transmission of messages. =20 *****************************************************************************= ************************************* --===============3439879485067003788==-- From Wim.Nelis@nlr.nl Wed Jun 24 08:21:39 2026 From: Wim.Nelis@nlr.nl To: xymon@xymon.com Subject: [Xymon] List of graphs of a devmon test is too long Date: Mon, 12 Mar 2012 15:49:17 +0100 Message-ID: <4F5E0CED.1070108@nlr.nl> In-Reply-To: <4F461693.3060802@nlr.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4716084377248731600==" --===============4716084377248731600== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, A follow-up on my own question: > we are using xymon 4.3.7 and devmon 0.3.1-beta1, r233. Some of the > devmon tests on interfaces of switches and routers use the rrd collector > of xymon. Those tests contain thus both a table and additionally one > graph per interface. However, for *each* test using the devmon rrd > collector there are three additional pointers to non-existing graphs. > The number of additional non-existing graphs is thus independent of the > number of interfaces being monitored. > > The following is the page source of a test to check for packet drops on > 3 interfaces of a router: > >

Thu 2012.02.23 10:58:22

> 
>
> Interface discards:
> Input  discard load alert thresholds: yellow=3D5.0%, red=3D10.0%
> Output discard load alert thresholds: yellow=3D5.0%, red=3D10.0%
>
> 
>   ...
>
>   ...
>   ...
>
>   ...
>   ...
>
> 
If namePacket rate in
eth010.55
eth118.05
eth20.00
wlan04.37

> 
>
> Note:
> Discard rate: Number of discards per second
> Discard load: Number of discards per packet
>
>
> Devmon version 0.3.1-beta1-r233 running on sodn164u
>
>
>
>

> > >
Status unchang= ed in 6 days,21 hours, 2 minutes
> Status message received from 137.17.28.26
>
> >
> > The (very) long lines have been truncated, at the "...", to enhance the > readability. In subdirectory ~xymon/data/rrd/nlrcve02-lan there are 3 > RRDs, not 6. > > How xymon does determine the linecount, 6 in the example above, is not > clear to me. However, it is the number of lines in the HTML comment > section containing the RRD data, which is always 3 more than the number > of interfaces. > > How can I configure xymon in such a way that the number of graphs > matches the number of interfaces? I've modified Devmon to send a linecount too. The patch to module=20 dm-tests.pm is: Index: dm_tests.pm =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- dm_tests.pm (revision 85) +++ dm_tests.pm (working copy) @@ -2118,10 +2119,11 @@ for my $name (keys %rrd) { my $set_data =3D ''; - my $temp_data =3D ''; + my $temp_data=3D ''; my $dir =3D $rrd{$name}{'dir'}; my $pri =3D $rrd{$name}{'pri'}; my $do_max =3D $rrd{$name}{'do_max'}; + my $linecount=3D 0 ; do_log("Couldn't fetch primary oid for rrd set $name") and next if $pri eq 'pri'; @@ -2151,10 +2153,12 @@ $set_data .=3D "$pri_val "; $set_data .=3D "$temp_data"; $set_data =3D~ s/:$/\n/; + $linecount++ ; } $set_data =3D~ s/[\/&+\$]/_/gs; + $msg .=3D "\n" ; $msg .=3D "$header\n$set_data-->\n"; } Using this patch, there are no more broken graphs. Regards, Wim Nelis. *****************************************************************************= ************************************* The NLR disclaimer is valid for NLR e-mail messages. This message is only meant for providing information. Nothing in this e-mail = message amounts to a contractual or legal commitment on the part of the sender. This message may contain information that is not intended for you. If you are= not the addressee or if this message was sent to you by mistake, you are requested to inform the sender an= d delete the message. Sender accepts no liability for damage of any kind resulting from the risks i= nherent in the electronic transmission of messages. =20 *****************************************************************************= ************************************* --===============4716084377248731600==--