Xymon Mailing List Archive search

Specify DNS timeout ?

3 messages in this thread

list Ken Connell · Fri, 7 Oct 2011 01:02:40 +0000 ·
Can I increase the timeout for a DNS test for just one particular server ?

We currently monitor 3 in-house and a 4th sits off-campus which timeouts sometimes...which I'm too worried about...
 
   
Ken Connell
Intermediate Network Engineer
Computer & Communication Services
Ryerson University
XXX Victoria St
RM AB50
Toronto, Ont
M5B 2K3
XXX-XXX-XXXX x6709
list Jeremy Laidman · Tue, 11 Oct 2011 17:24:31 +1100 ·
quoted from Ken Connell
On Fri, Oct 7, 2011 at 12:02 PM,  <user-7cb0f5662626@xymon.invalid> wrote:
Can I increase the timeout for a DNS test for just one particular server ?

We currently monitor 3 in-house and a 4th sits off-campus which timeouts sometimes...which I'm too worried about...
Short of scripting up a special test, I doubt it.

However, you can de-sensitise the DNS alarms on a per-host basis by
using the "badTEST" construct.  For example this is what I have on
some of my hosts that have occasional problems:

  10.1.12.10   ssm001.bogus.example.com        # baddns:1:2:3
dns=SOA:bogus.example.com

The "baddns:1:2:3" means it goes clear after 1 failure, yellow after 2
failures and red only after 3 successive failures.

Cheers
Jeremy
list Ken Connell · Wed, 12 Oct 2011 00:44:57 +0000 ·
The "baddns:1:2:3" tag worked great...I do get the "clear" tests/value here and there but no one is in "panic mode" with false "red" alerts :)

Thanks 
quoted from Jeremy Laidman
------Original Message------
From: Jeremy Laidman
To: Ken Connell
Cc: Xymon Email List
Subject: Re: [Xymon] Specify DNS timeout ?
Sent: Oct 11, 2011 2:24 AM

On Fri, Oct 7, 2011 at 12:02 PM,  <user-7cb0f5662626@xymon.invalid> wrote:
Can I increase the timeout for a DNS test for just one particular server ?

We currently monitor 3 in-house and a 4th sits off-campus which timeouts sometimes...which I'm too worried about...
Short of scripting up a special test, I doubt it.

However, you can de-sensitise the DNS alarms on a per-host basis by
using the "badTEST" construct.  For example this is what I have on
some of my hosts that have occasional problems:

  10.1.12.10   ssm001.bogus.example.com        # baddns:1:2:3
dns=SOA:bogus.example.com

The "baddns:1:2:3" means it goes clear after 1 failure, yellow after 2
failures and red only after 3 successive failures.

Cheers
Jeremy

   
Ken Connell
Intermediate Network Engineer
Computer & Communication Services
Ryerson University
XXX Victoria St
RM AB50
Toronto, Ont
M5B 2K3
XXX-XXX-XXXX x6709