Jump to content


Custom Monitor Timeout

  • Please log in to reply
1 reply to this topic

#1 Steve s

Steve s


  • Members
  • Pip
  • 3 posts
  • Gender:Male
  • Location:Hampshire

Posted 10 November 2011 - 03:45 PM


I have written a custom monitor with retained data. The reporting mechanism is working properly - i.e. I can retrieve values from my remote node and store the results. Howerver the monitor noly works when I run a dummy script that returns the results in a couple of seconds. The real script that I need to run takes approximately 30 seconds to complete and I always get "Read timed out" when try and test it. The timeout is always around 17 seconds. I've tried setting the "Timeout" to 600 seconds but it seems to have no effect at all. After 17 seconds I get "Read timed out" again.

Is there another setting where I can change the Timeout value?

Any help would be appreciated

#2 Joel Pereira

Joel Pereira


  • Members
  • PipPipPipPip
  • 174 posts
  • Gender:Male
  • Location:Toronto, Canada

Posted 10 November 2011 - 04:28 PM

What is the mechanism you're using to retrieve the value?
Is there a custom script running on a remote system, and are you executing the script via the up.time agent? If so, what kind of agent?

For example, Windows agents are set to timeout after 15 seconds by default. This can be changed with the Agent Console on the remote agent system.
Joel Pereira
Solutions Architect
uptime software ...because downtime is not an option

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users