Testing in production, or live-testing your web app using live customer traffic, is a test strategy that app developers increasingly integrate into their agile development methodology. It enables you to test the quality of your apps with live user traffic in your production environment, as opposed to synthesized data in a test environment. By exposing your new app to real users, you can be informed on the real problems your app may face once it is deployed. You can verify the functionality, performance, and value of your app updates against the volume, velocity, and variety of real user traffic, which you can never approximate in a test environment.
Traffic Routing in App Service Web Apps
With the Traffic Routing feature in Azure App Service, you can direct a portion of live user traffic to one or more deployment slots, and then analyze your app with Azure Application Insights or Azure HDInsight, or a third-party tool like New Relic to validate your change. For example, you can implement the following scenarios with App Service:
- Discover functional bugs or pinpoint performance bottlenecks in your updates prior to site-wide deployment
- Perform "controlled test flights" of your changes by measuring usability metrics on the beta app
- Gradually ramp up to a new update, and gracefully back down to the current version if an error occurs
- Optimize your app's business results by running A/B tests or multivariate tests in multiple deployment slots
Requirements for using Traffic Routing in Web Apps
- Your web app must run in Standard or Premium tier, as it is required for multiple deployment slots.
- Traffic Routing supports advanced TiP scenarios through Azure PowerShell cmdlets.
Route traffic segment to a deployment slot
At the basic level in every TiP scenario, you route a predefined percentage of your live traffic to a non-production deployment slot. To do this, follow the steps below:
- Log into the Azure Portal.
- In your web app's blade, click Settings > Traffic Routing.
Select the slot that you want to route traffic to and the percentage of the total traffic you desire, then click Save.
Go to the deployment slot's blade. You should now see live traffic being routed to it.
Once Traffic Routing is configured, the specified percentage of clients will be randomly routed to your non-production slot. However, it is important to note that once a client is automatically routed to a specific slot, it will be "pinned" to that slot for the life of that client session. This done using a cookie to pin the user session. If you inspect the HTTP requests, you will find a
TipMix cookie in every subsequent request.
Force client requests to a specific slot
In addition to automatic traffic routing, App Service is able to route requests to a specific slot. This is useful when you want your users to be able to opt-into or opt-out of your beta app. To do this, you use the
x-ms-routing-name query parameter.
To reroute users to a specific slot using
x-ms-routing-name, you must make sure that the slot is already added to the Traffic Routing list. Since you want to route to a slot explicitly, the actual routing percentage you set doesn't matter. If you want, you can craft a "beta link" that users can click to access the beta app.
Opt users out of beta app
To let users opt out of your beta app, for example, you can put this link in your web page:
<a href="<webappname>.azurewebsites.net/?x-ms-routing-name=self">Go back to production app</a>
x-ms-routing-name=self specifies the production slot. Once the client browser access the link, not only is it redirected to the production slot, but every subsequent request will contain the
x-ms-routing-name=self cookie that pins the session to the production slot.
Opt users in to beta app
To let users opt in to your beta app, set the same query parameter to the name of the non-production slot, for example: