how to add a specific http timeout 🔗 link

On 31-01-2012 09:25, Nicolas LIENARD wrote:

Currently, xymonnet is running with a global timeout of 20 seconds
(--timeout=20).

For a particular device, i need to increase the HTTP timeout (120
seconds.. sic).

I did't find anything regarding this kind of feature. only a old mail of
2006 saying it's not possible.
(http://lists.xymon.com/archive/2006-August/009042.html).

Is it still not possible to override this timeout individually ?

Le 31 janv. 2012 à 09:55, Henrik Størner a écrit :

On 31-01-2012 09:25, Nicolas LIENARD wrote:

Currently, xymonnet is running with a global timeout of 20 seconds
(--timeout=20).

For a particular device, i need to increase the HTTP timeout (120
seconds.. sic).

I did't find anything regarding this kind of feature. only a old mail of
2006 saying it's not possible.
(http://lists.xymon.com/archive/2006-August/009042.html).

Is it still not possible to override this timeout individually ?

No, this will be possible in the next release - but not in 4.3.x.

What you can do is to use the "NET:foo" definition on this particular host in hosts.cfg to have it tested by a special instance of the xymonnet task:

1) Add the "--test-untagged" option to your current xymonnet command in tasks.cfg

2) Add "NET:slowtests" to this particular host in hosts.cfg

3) In a script, set XYMONNETWORK="slowtests" (remember to export it!) and then run the xymonnet command to do the test of this one host, with the different --timeout option

4) Add a new section to tasks.cfg to run the test script.


Regards,
Henrik

1) Add the "--test-untagged" option to your current xymonnet command
in tasks.cfg

2) Add "NET:slowtests" to this particular host in hosts.cfg

3) In a script, set XYMONNETWORK="slowtests" (remember to export it!)
and then run the xymonnet command
to do the test of this one host, with the different --timeout option

4) Add a new section to tasks.cfg to run the test script.

 
Neil Simmonds

Operation Analyst (Operations Support Group)
Express Gifts Limited

Express House

Clayton Business Park

Accrington

Lancashire

BB5 5JY 
T: 01254 303092 | E: user-8188d25e65e4@xymon.invalid 

 

 
I've been looking at setting one of our systems to have a different
timeout on the http test to the default 10 seconds.

 
I've followed the instructions from Henrik,

 

1) Add the "--test-untagged" option to your current xymonnet command
in tasks.cfg

2) Add "NET:slowtests" to this particular host in hosts.cfg

3) In a script, set XYMONNETWORK="slowtests" (remember to export it!)
and then run the xymonnet command
to do the test of this one host, with the different --timeout option

4) Add a new section to tasks.cfg to run the test script.

 
Yet it's not working. 

 
This is my xymonnet entry in tasks.cfg

 
[xymonnet]

        ENVFILE /xymon/server/etc/xymonserver.cfg

        NEEDS xymond

        CMD xymonnet --report --ping --checkresponse --test-untagged

        LOGFILE $XYMONSERVERLOGS/xymonnet.log

        INTERVAL 5m

 
My entry in hosts.cfg looks like this,

 
***.**.**.**    Matrix        #
http://***.**.**.**:8080/4daction/getImageData?u=419520 NET:slowtests

 
My script looks like this,

 
#!/bin/sh

 
XYMONNETWORK="slowtests"

export XYMONNETWORK

 
$XYMONHOME/bin/xymonnet --report --ping --checkresponse --timeout=20

 
And finally my extra entry in tasks.cfg looks like this,

 
## Xymonnet test with 20 second timeout

[slowtests]

        ENVFILE /xymon/server/etc/xymonserver.cfg

        NEEDS xymond

        CMD $XYMONHOME/ext/slowtests.sh

        LOGFILE $XYMONSERVERLOGS/slowtests.log

        INTERVAL 5m

 
This is all running on Xymon 4.3.4

 
Can anyone spot where I might have gone wrong.

 
Thanks,

 
Neil Simmonds

Operation Analyst (Operations Support Group)
Express Gifts Limited

Express House

Clayton Business Park

Accrington

Lancashire

BB5 5JY 
T: 01254 303092 | E: user-8188d25e65e4@xymon.invalid 

 
Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE,
CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151.

Express Gifts Limited is authorised and regulated by the Financial
Services Authority


NOTE: This email and any information contained within or attached in a
separate file is confidential and intended solely for the Individual to
whom it is addressed. The information or data included is solely for the
purpose indicated or previously agreed. Any information or data included
with this e-mail remains the property of Findel PLC and the recipient
will refrain from utilising the information for any purpose other than
that indicated and upon request will destroy the information and remove
it from their records. Any views or opinions presented are solely those
of the author and do not necessarily represent those of Findel PLC. If
you are not the intended recipient, be advised that you have received
this email in error and that any use, dissemination, forwarding,
printing, or copying of this email is strictly prohibited. No warranties
or assurances are made in relation to the safety and content of this
e-mail and any attachments. No liability is accepted for any
consequences arising from it. Findel Plc reserves the right to monitor
all e-mail communications through its internal and external networks. If
you have received this email in error please notify our IT helpdesk on
+44(0) 1254 303030

 
Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151.
Express Gifts Limited is authorised and regulated by the Financial Services Authority
NOTE:  This email and any information contained within or attached in a separate file is confidential and intended solely for the 
Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any 
information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the 
information for any purpose other than that indicated and upon request will destroy the information and remove it from their records.  
Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not 
the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, 
or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this 
e-mail and any attachments.  No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor 
all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT 
helpdesk on +44(0) 1254 303030

"No, this will be possible in the next release - but not in 4.3.x.

What you can do is to use the "NET:foo" definition on this particular
host in hosts.cfg to have it tested by a special instance of the
xymonnet task:

1) Add the "--test-untagged" option to your current xymonnet command in
tasks.cfg

2) Add "NET:slowtests" to this particular host in hosts.cfg

3) In a script, set XYMONNETWORK="slowtests" (remember to export it!)
and then run the xymonnet command to do the test of this one host, with
the different --timeout option

4) Add a new section to tasks.cfg to run the test script."

On 5/6/2019 2:14 AM, José Manuel Blasco Díaz wrote:

Good Morning.

I run Xymon 4.3.25 and I need to enable an alert for http 8280 when timeout is over 1 second.

Can I do easily way in hosts or I have to create a new configuration as you explain in olders version?

“No, this will be possible in the next release - but not in 4.3.x.

What you can do is to use the "NET:foo" definition on this particular

host in hosts.cfg to have it tested by a special instance of the

xymonnet task:

1) Add the "--test-untagged" option to your current xymonnet command in

tasks.cfg

2) Add "NET:slowtests" to this particular host in hosts.cfg

3) In a script, set XYMONNETWORK="slowtests" (remember to export it!)

and then run the xymonnet command to do the test of this one host, with

the different --timeout option

4) Add a new section to tasks.cfg to run the test script.”

Thanks.

Best Regards.

JoseManuelBlasco