http health monitor

Mayank, if you are running a pool with port 80 or 8000, the string you send usually depends on the application you are running. For instance, a majority of applications have a /hello file somewhere within (this is true for Oracle EBS) and you can have the string grab that in order to verify the server is accessible.

 

The base HTTP monitor does a simple get which can sometimes be misleading. So adding an extra send string and what you expect to receive can help validate the server accessibility!

 

Sorry, did this as a comment as opposed to an answer.

 

Mayank, if you are running a pool with port 80 or 8000, the string you send usually depends on the application you are running. For instance, a majority of applications have a /hello file somewhere within (this is true for Oracle EBS) and you can have the string grab that in order to verify the server is accessible.

 

The base HTTP monitor does a simple get which can sometimes be misleading. So adding an extra send string and what you expect to receive can help validate the server accessibility!

 

HTTP monitor basically works by probing to a file in the server/application.

 

For example. If the server has a file named probecheck.html and we need to check if the server is good at serving the page. Send string will be:

 

I am assuming using HTTP/1.1

 

GET /probecheck.html HTTP/1.1\r\nHost:host.domain.com\r\nConnection:Close\r\n\r\n

 

If we just wan to check the page exist i.e. we can look for 200 OK back from the servr.

 

Receive: HTTP/1.1 200 OK

 

If we want to check some text written on the page/file for example probecheck.html has a text ON then we can have a receive string as:

 

Receive: ON

 

More information on HTTP monitor: https://support.f5.com/csp/article/K13397