xymon test dependencies
list Taylor Lewick
From the xymon.com webpage is this snippit...
---
Combined super-tests and test interdependencies
...
Tests can also be configured to depend on each other, so that when a
critical router goes down you will get alerts only for the router - and
not from the 200 hosts behind the router.
---
I'm not seeing how to set this type of testing up, basically event
correlation, so that if a switch goes down, hobbit knows not to send
alerts for each connected host.
Can some point me in the right direction, i.e. specific man-page, or
just show me an example of how to configure this?
Thanks,
Taylor
list Johan Sjöberg
Hi. Use the "route" setting. For each connected device, add "route:switch.company.com". That way, if the conn test of the switch fails, any conn test for the connected devices will go yellow instead of red. /Johan
▸
-----Original Message-----
From: Taylor Lewick [mailto:user-ccbabb0b3ab0@xymon.invalid]
Sent: den 13 oktober 2010 18:01
To: xymon at xymon.com
Subject: [xymon] xymon test dependencies
From the xymon.com webpage is this snippit...
---
Combined super-tests and test interdependencies ...
Tests can also be configured to depend on each other, so that when a critical router goes down you will get alerts only for the router - and not from the 200 hosts behind the router.
---
I'm not seeing how to set this type of testing up, basically event correlation, so that if a switch goes down, hobbit knows not to send alerts for each connected host.
Can some point me in the right direction, i.e. specific man-page, or just show me an example of how to configure this?
Thanks,
Taylor
list Taylor Lewick
OK, thanks, any opinions on whether it is better to use route, or depends?
▸
-----Original Message-----
From: Johan Sjöberg [mailto:user-74c177c1220d@xymon.invalid]
Sent: Wednesday, October 13, 2010 12:34 PM
To: xymon at xymon.com
Subject: [xymon] RE: xymon test dependencies
Hi.
Use the "route" setting. For each connected device, add "route:switch.company.com". That way, if the conn test of the switch fails, any conn test for the connected devices will go yellow instead of red.
/Johan
-----Original Message-----
From: Taylor Lewick [mailto:user-ccbabb0b3ab0@xymon.invalid]
Sent: den 13 oktober 2010 18:01
To: xymon at xymon.com
Subject: [xymon] xymon test dependencies
From the xymon.com webpage is this snippit...
---
Combined super-tests and test interdependencies ...
Tests can also be configured to depend on each other, so that when a critical router goes down you will get alerts only for the router - and not from the 200 hosts behind the router.
---
I'm not seeing how to set this type of testing up, basically event correlation, so that if a switch goes down, hobbit knows not to send alerts for each connected host.
Can some point me in the right direction, i.e. specific man-page, or just show me an example of how to configure this?
Thanks,
Taylor
list Patrick Nixon
Last I checked, the depends wasn't working properly and I haven't seen a release. --Patrick On Wed, Oct 13, 2010 at 1:54 PM, Taylor Lewick
▸
<user-ccbabb0b3ab0@xymon.invalid>wrote:
OK, thanks, any opinions on whether it is better to use route, or depends? -----Original Message----- From: Johan Sjöberg [mailto:user-74c177c1220d@xymon.invalid] Sent: Wednesday, October 13, 2010 12:34 PM To: xymon at xymon.com Subject: [xymon] RE: xymon test dependencies Hi.
Use the "route" setting. For each connected device, add "route:
switch.company.com". That way, if the conn test of the switch fails, any
▸
conn test for the connected devices will go yellow instead of red.
/Johan
-----Original Message-----
From: Taylor Lewick [mailto:user-ccbabb0b3ab0@xymon.invalid]
Sent: den 13 oktober 2010 18:01
To: xymon at xymon.com
Subject: [xymon] xymon test dependencies
From the xymon.com webpage is this snippit...
---
Combined super-tests and test interdependencies ...
Tests can also be configured to depend on each other, so that when a
critical router goes down you will get alerts only for the router - and not
from the 200 hosts behind the router.
---
I'm not seeing how to set this type of testing up, basically event
correlation, so that if a switch goes down, hobbit knows not to send alerts
for each connected host.
Can some point me in the right direction, i.e. specific man-page, or just
show me an example of how to configure this?
Thanks,
Taylor
list Marco Avvisano
Hi,
I changed the name of the image with the image, and I made it clickable
168,180c172,173
< if (showcolors) {
< printf(" - ");
< if (addlink) {
< printf("<a href=\"%s\">",
hostsvcurl(hostname, testname, 1));
< printf("<img src=\"/gifs/%s", colorstr);
< printf(".gif\" width=\"16\" height=\"16\"
border=0 alt=\"%s\"", colorstr);
< printf("title=\"%s\"", colorstr);
< printf("></a>");
< }
< else {
< printf("<IMG SRC=\"/gifs/%s", colorstr);
< printf(".gif\" >");
< }
--- if (showcolors) printf(" - %s", colorstr);
Marco
list Buchan Milne
▸
On Wednesday, 13 October 2010 19:06:08 Patrick Nixon wrote:
Last I checked, the depends wasn't working properly and I haven't seen a release.
This works for me: a.b.c.d dnscache1.xxxx # dns=a:www.google.com testip depends=(dns:UPSTREAMLINK/conn) (where UPSTREAMLINK is the name of a bb-hosts entry that has a conn check for our next hop(s)). If UPSTERAMLINK.conn is red, and the dns test fails, it goed clear instead of red (well, it can be red for a brief period, so one should alert on red with DURATION greater than the time your bbtest-net cycle actually takes - in my case the time taken when DNS is unavailable) If you have a case where it is not working according to the documentation, please discuss and file a bug if necessary. Note though that depends only works for tests run by bbtest-net, AFAIK you can't have a network check depending on a ports (client data) check, or have one host checked by one bbtest-net instance depend on a network test checked by another bbtest-net instance. This is covered in the bb-hosts(5) coverage for the 'depends' tag. Regards, Buchan
list Marco Avvisano
▸
Il 14/10/2010 11.09, Buchan Milne ha scritto:
On Wednesday, 13 October 2010 19:06:08 Patrick Nixon wrote:Last I checked, the depends wasn't working properly and I haven't seen a release.This works for me: a.b.c.d dnscache1.xxxx # dns=a:www.google.com testip depends=(dns:UPSTREAMLINK/conn) (where UPSTREAMLINK is the name of a bb-hosts entry that has a conn check for our next hop(s)). If UPSTERAMLINK.conn is red, and the dns test fails, it goed clear instead of red (well, it can be red for a brief period, so one should alert on red with DURATION greater than the time your bbtest-net cycle actually takes - in my case the time taken when DNS is unavailable) If you have a case where it is not working according to the documentation, please discuss and file a bug if necessary. Note though that depends only works for tests run by bbtest-net, AFAIK you can't have a network check depending on a ports (client data) check, or have one host checked by one bbtest-net instance depend on a network test checked by another bbtest-net instance. This is covered in the bb-hosts(5) coverage for the 'depends' tag.
It would be great if it could work for all the test Marco
Regards, Buchan