Azure Traffic Manager—Fast Failover and TCP Probing
Date Updated: Monday, July 3, 2017
Two new features in Azure Traffic Manager are now generally available—Fast Failover and TCP Probing.
With Fast Failover, you'll be able to choose to have faster redirection of your users away from an endpoint that has become unhealthy. Specifically, you'll be able to:
· Choose a shorter interval of 10 seconds for Traffic Manager to check endpoint health status (versus the default 30 seconds).
· Configure the number of tolerated failures (from 0 to 9) that should happen consecutively before endpoint is marked as unhealthy.
· Configure the time-out interval for each probe attempt (from 5 to 9 seconds if the probe interval is 10 seconds, and from 5 to 10 seconds if probe interval is 30 seconds).
· Set the Time to Live (TTL) response all the way down to 0.
Choosing to use the fast interval of 10 seconds for the health checks will cost an extra $1 per endpoint per month for checking Azure endpoints, and an extra $2 per endpoint per month for external endpoints. Please visit the Azure Traffic Manager pricing page for more details.
With TCP Probing, you'll be able to choose to have Traffic Manager determine your endpoints’ health by listening to responses for a TCP connection request. You could then add to Traffic Manager profiles those endpoints that do not have the ability to respond to HTTP health checks, such as back-end databases. This feature will help you reduce the resource usage in your endpoints because it will typically have a lower overhead. There's no additional charge for using this feature.
You can access the settings for Fast Failover and TCP Probing by using the Azure portal, PowerShell, CLI, and REST APIs/SDKs.
To start using these features, see the endpoint monitoring documentation for Traffic Manager.