NetXMS Support Forum

Hello,

I have configured ServiceCheck.HTTPS to monitor status of internal web application every minute. It works fine when application is UP (returned value = 0) and when application is shut-down for maintenance reasons (returned value = 2). Unfortunately it does not work if application is overloaded and web page is almost not accessible (rendering web page takes 5-10 seconds).

No matter what timeout value I configure (I tried: 1000, 3000, 5000) NetXMS is not returning any status.
Below is the example history of collected data.
"Timestamp","Value"
"10.04.2015 12:20:23","0"
"10.04.2015 12:09:23","0"
"10.04.2015 12:05:23","0"
"10.04.2015 12:01:23","0"
"10.04.2015 11:55:23","0"
"10.04.2015 11:54:23","0"
"10.04.2015 11:52:23","0"
"10.04.2015 11:51:23","0"
"10.04.2015 11:50:23","0"
"10.04.2015 11:49:23","0"
"10.04.2015 11:48:23","0"
"10.04.2015 11:47:23","0"
"10.04.2015 11:46:23","0"
"10.04.2015 11:45:23","0"
"10.04.2015 11:44:23","0"
"10.04.2015 11:43:23","0"
"10.04.2015 11:42:23","0"
"10.04.2015 11:41:23","0"
"10.04.2015 11:40:23","0"
"10.04.2015 11:39:23","0"
"10.04.2015 11:38:23","0"
"10.04.2015 11:37:23","0"
"10.04.2015 11:36:23","0"
"10.04.2015 11:35:23","0"
"10.04.2015 11:34:23","0"
"10.04.2015 11:33:23","0"
"10.04.2015 11:32:23","0"
"10.04.2015 11:31:23","0"
"10.04.2015 11:30:23","0"

At the beginning it works fine. Checks are executed every minute, but later around 12:00, when website is not responsive at all, timestamp changes from 1 minuted to several minutes.

I'm using NetXMS 2.0-M2.

How this issue can be resolved?

Best regards,
Marcin

Hi,

try to increase value for server configuration parameter AgentCommandTimeout (it defines how long server will wait for response from agent, in milliseconds).

Best regards,
Victor

Hi Victor,

I have seen this recommendation in one of your ealier replies.
This is why I tried with ServiceCheck.HTTPS timeout set to 1000 (AgentCommandTimeout = 4000).
I will try again.

Best regards,
Marcin