Longer timeout than 2 seconds.
We are sysadmin that use services like this + webhook to wake up sysadmins in the middle of the night if something goes down.
2 second max response is too short. Sometimes a server can become overloaded and be sluggish for a moment, and thats OK, and should not be considered a downtime.
If sysadmins are woken at 3am for a brief period of sluggishness, then they cant perform well the next day fully sleep deprived.
Need longer options. 3,4,5,..10 second ranges
This is not the timeout, this 2 sec max select box is about Apdex threshold and performance metrics.
At the time of writing the timeouts are:
- for HTTP and TCP checks: 10sec connection + 30sec response
- for ICMP checks: 4 pings with 5 sec timeout each (if any ping success the check is UP)
Again, this is not the timeout, as the tooltip says this is the Apdex threshold which is only used for performance monitoring. For ICMP checks, we perform 4 pings with 5 sec timeout at every check, and we need all 4 to fail to consider one check as failed. (and we still need 3 down check to send an alert).
Jason Wells commented
Here is an example of the timeout settings for an ICMP check. The max is 2.0 sec.
See attached file.
The response timeout is 30 seconds (and the TCP connection timeout is 10 seconds). What makes you think it's currently 2 seconds?