Is it possible to get response time of node?

Actually,

 

 

I think it's a bit more complex than fast response time is good and slow response time indicates a problem. An example to illustrate:

 

 

You have a pool of 10 servers. You are using fastest response (I prefer observed) for load balancing between them. You are not using anything other than basic monitors to determine if a node is available. The page weight of your index page in the doc root is 60k.

 

 

One of your servers has gotten foosed (that's a technical term) and is returning a 500 response. What happens?

 

 

The answer is that you will be serving a lot of bad pages very fast. In this scenario the Bigip will send more traffic to the bad node than to the good nodes. The same thing would happen if you were serving a 404 from one of the servers. Bigip will show all the nodes as up and available even though you are not properly serving the customer.

 

 

The other metric that might be of interest is the ratio of bits in to bits out for each node in a pool. The ratio should be roughly the same for each node (even if the absolute numbers vary because a node was temporarily out of service). We pull the data off the Bigip (to minimize load) and do some massaging to alert on variations outside of defined parameters. It's not perfect but we get very few false positives and do catch problems fairly quickly.

 

 

Dotzero