interval/up-interval vs timeout
Hello,
As mentionned in the summary, I would like to get some explanations on how the 'timeout' for an HTTP monitor will react when the up-interval value is set to a different value than the 'interval' one.
Iin my case, up-interval is bigger than interval.
I think I pretty get the story of the 3:1 ratio between timeout and interval, it helps to determine how many consecutive request must fail before declaring a server as down.
Interval of 5 and timeout of 16 means that after three failed checks, the resource is declared as down.
I am currently using values of 30sec for the interval (frequency) and 62 for the timeout (OK, not really a 3:1 ratio but proven to work)
Meaning that we wait for two consecutives failed HTTP checks before declaring a server as down.
My client asks me if we could keep 30 sec as interval when the server is up, but use a more 'aggressive' interval (5 sec in fact) in case of no reply from a server (within the timeout period).
I think to configure for this the 'up-interval' to 30sec, the (down) 'interval' to 5.
But I am not sure if "(down) interval" already applies when a member is failing (but still marked as up) or only after when marked as down ?
(I do not really have a test bed to play with values, any change occurs in our 'prod' environment)
Related to 1st question, I am wondering if, as for the "up-interval" and "(down) interval", there is a way to use two different timeout values: one when a member is up or down, one when a member is in a 'failing' state but not already declared as down ?
thanks and best regards,
--
Benoit