For Azure Traffic Manager to determine the health of your website endpoints (deployments) you need to provide some basic monitoring settings so that Azure Traffic Manager can query your endpoints to determine if an endpoint should be taken out of the rotation. The monitoring settings consist of the following:
■ Protocol This can be HTTP or HTTPS.
■ Port Use standard HTTP and HTTPS ports, such as 80 or 443.
■ Relative Path And File Name This is the path and ile name in the application that the monitoring service will perform an HTTP GET request against. This can be the root of the application, such as "/". Or, it could be a speciic health check page the application may make available, such as /Healthcheck.aspx.
USING HEALTH CHECK PAGES TO DETERMINE WEBSITE HEALTH
Some websites provide a health check page as part of the application and may name the page Healthcheck.aspx. The advantage of having a health check page is that the page can check the health of other services the application depends on, such as SQL Database connections, web service availability, or internal metrics the application developers have added as part of the health monitoring of the application. Just because a request for a page such as the root at "/" may return an HTTP 200 (OK), doesn't necessarily mean the application is healthy.
By using a custom health check page, applications can more accurately determine the health of the application instance and return an error code, such as HTTP 503 (Service Unavailable). As a result, Azure Traffic Manager will remove the endpoint from the rotation until the application instance returns HTTP 200 (OK).
■ Protocol This can be HTTP or HTTPS.
■ Port Use standard HTTP and HTTPS ports, such as 80 or 443.
■ Relative Path And File Name This is the path and ile name in the application that the monitoring service will perform an HTTP GET request against. This can be the root of the application, such as "/". Or, it could be a speciic health check page the application may make available, such as /Healthcheck.aspx.
USING HEALTH CHECK PAGES TO DETERMINE WEBSITE HEALTH
Some websites provide a health check page as part of the application and may name the page Healthcheck.aspx. The advantage of having a health check page is that the page can check the health of other services the application depends on, such as SQL Database connections, web service availability, or internal metrics the application developers have added as part of the health monitoring of the application. Just because a request for a page such as the root at "/" may return an HTTP 200 (OK), doesn't necessarily mean the application is healthy.
By using a custom health check page, applications can more accurately determine the health of the application instance and return an error code, such as HTTP 503 (Service Unavailable). As a result, Azure Traffic Manager will remove the endpoint from the rotation until the application instance returns HTTP 200 (OK).
