A monitor defines a health test method for an application (IP Endpoint). For example, using the HTTP protocol, the monitor will send a test string to a specific port for the IP endpoint, and then it evaluates the received string against the expected receive string. Different protocols will have different options for testing the application. IP endpoints that don’t respond, take too long to respond, or don’t return the correct information will be marked as unhealthy so that the load balancer doesn’t use them for end-user request results.
Enter the following values for the monitor properties:
- Name this monitor - you will use this name when setting up the IP endpoints.
- Add notes here - this allows you to store additional information about this monitor.
- Choose protocol - the protocol will determine the other data entry required
Some protocols can be standard or advanced, whereas other protocols are only available in standard form. Standard protocols will use simple, common methods to determine the help of the application. Advanced protocols will allow you to specify both a send and a receive string for more advanced determination. Note that advanced monitors also incur added charges.
For more information, see Details for creating an application health monitor.