Traffic Manager Real User Measurements overview
When you set up a Traffic Manager profile to use the performance routing method, the service looks at where the DNS query requests are coming from and makes routing decisions to direct those requestors to the Azure region that gives them the lowest latency. This is accomplished by utilizing the network latency intelligence that Traffic Manager maintains for different end-user networks.
Real User Measurements enables you to measure network latency measurements to Azure regions, from the client applications your end users use, and have Traffic Manager consider that information as well when making routing decisions. By choosing to use the Real User Measurements, you can increase the accuracy of the routing for requests coming from those networks where your end users reside.
How Real User Measurements work
Real User Measurements work by having your client applications measure latency to Azure regions as it is seen from the end-user networks in which they are used. For example, if you have a web page that is accessed by users across different locations (for example, in the North American regions), you can use Real User Measurements with performance routing method to get them to the best Azure region in which your server application is hosted.
Over time, this happens many times and across many networks leading to Traffic Manager getting more accurate information about the latency characteristics of the networks in which your end users reside. This information starts getting to be included in the routing decisions made by Traffic Manager. As a result, it leads to increased accuracy in those decisions based on the Real User Measurements sent.
When you use Real User Measurements, you are billed based on the number of measurements sent to Traffic Manager. For more details on the pricing, visit the Traffic Manager pricing page.
Do I need to enable Real User Measurements each profile separately?
How do I turn off Real User Measurements for my subscription?
Can I use Real User Measurements with client applications other than web pages?
How many measurements are made each time my Real User Measurements enabled web page is rendered?
Is there a delay before Real User Measurements script runs in my webpage?
Can I use Real User Measurements with only the Azure regions I want to measure?
Can I limit the number of measurements made to a specific number?
Can I see the measurements taken by my client application as part of Real User Measurements?
Can I modify the measurement script provided by Traffic Manager?
Will it be possible for others to see the key I use with Real User Measurements?
Can information about my end users be identified by Traffic Manager if I use Real User Measurements?
Does the webpage measuring Real User Measurements need to be using Traffic Manager for routing?
Do I need to host any service on Azure regions to use with Real User Measurements?
Will my Azure bandwidth usage increase when I use Real User Measurements?
- Learn how to use Real User Measurements with web pages
- Learn how Traffic Manager works
- Learn more about Mobile Center
- Learn more about the traffic-routing methods supported by Traffic Manager
- Learn how to create a Traffic Manager profile
Submit and view feedback for