Professional Documents
Culture Documents
By
Reviewers
Name Version Approved Date
Traffic Manager uses DNS to direct client requests to the most appropriate service endpoint
based on a traffic-routing method and the health of the endpoints. An endpoint is any Internet-
facing service hosted inside or outside of Azure. Traffic Manager provides a range of traffic-
routing methods and endpoint monitoring options to suit different application needs and
automatic failover models. Traffic Manager is resilient to failure, including the failure of an
entire Azure region.
Azure Traffic Manager supports six traffic-routing methods to determine how to route network
traffic to the various service endpoints. For any profile, Traffic Manager applies the traffic-
routing method associated to it to each DNS query it receives. The traffic-routing method
determines which endpoint is returned in the DNS response.
Following components have been deployed for the Traffic Manager Solution.
EastUS Region
Resource Group: Traffic-Manager-RG
VNET
WEB Subnet
AV SET
Windows 2012 VM with a Public IP assigned
Install and Configure Webserver (IIS)
Traffic Manager Profile
The following features of Azure Traffic Manager helps in configuring the Load Balancer.
2.1 Configuration
Configuration tab under settings is used to configure the Routing Method, DNS TTL value in
seconds, Protocol for End Point Monitoring, Port 80 or 443 (if SSL), path & probing interval time
in seconds
Understand where your user bases are located (up to a local DNS resolver level
granularity).
View the volume of traffic (observed as DNS queries handled by Azure Traffic Manager)
originating from these regions.
Get insights into what is the representative latency experienced by these users.
Deep dive into the specific traffic patterns from each of these user bases to Azure
regions where you have endpoints.
2.3 Endpoints
Microsoft Azure Traffic Manager allows you to control how network traffic is distributed to
application deployments running in different datacenters. You configure each application
deployment as an 'endpoint' in Traffic Manager. When Traffic Manager receives a DNS request,
it chooses an available endpoint to return in the DNS response. Traffic manager bases the
choice on the current endpoint status and the traffic-routing method.
In addition to the above metrics we can configure Alerts, based on the metrics and activity logs
alerts will be sent to the specified email address.
2.5 Resource Health
Resource Health Section helps to diagnose and get support when an Azure issue impacts the
resources. It informs about the current and past health of the resource and helps to mitigate
issues. Resource health provides technical support when we need help with Azure service
issues.
Resource Health gives us a personalized dashboard of the health of the resource. Resource
Health shows all the times the resource was unavailable in the past because of Azure service
problems.
2.6 Test Results
c) Website hosted on “South East Asia” Webserver accessed using the Public IP
d) Website accessed using the Traffic Manager FQDN
Note: In production scenario, we would create a CNAME record in our Public DNS pointing to
the Traffic Manager FQDN
e) As the website is browsed from India, the webpage is presented from the South East
Asia Datacenter.
g) The Endpoint monitoring fails after the South East Asia Web Server is Stopped.
h) Website Access using the Traffic Manager FQDN after the South East Asia Web Server is
stopped, the Traffic Manager directs the traffic to the East US Datacenter.
2.7 Pricing
Traffic Manager billing is based on the following pricing dimensions:
1. The number of DNS queries received, with a discount for services receiving more than 1
billion monthly queries.
2. The number of monitored endpoints. The rate depends on (1) whether it’s an Azure or
external service and (2) how frequently you want Traffic Manager to monitor the
endpoint.
3. The number of real user measurements received by the Traffic Manager Service.
PRICE
First 1 billion DNS queries/month ₹35.692 per million queries
Over 1 billion DNS queries/month ₹24.787 per million queries
Basic Health Checks
₹23.795 per Azure
Basic health checks (Azure) endpoint/month
₹66.097 per Azure
Fast interval health checks add-on (Azure) endpoint/month
₹35.692 per external
Basic health checks (external) endpoint/month
₹132.193 per external
Fast interval health checks add-on (external)1 endpoint/month
Traffic Manager Real User Measurements currently supports
measuring only Azure regions.
REAL USER MEASUREMENTS
₹132.193 per million
Measuring Azure Regions measurements
TRAFFIC VIEW
₹132.193 per million data
Data points processed points processed
https://azure.microsoft.com/en-us/pricing/details/traffic-manager/
For detailed documentation on Azure Traffic Manager follow the below link
https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview