Configure Traffic Split Verification
You can configure verification using the traffic split mechanism during the Workflow definition phase.
In this topic:
- Before You Begin
- Step 1: Add the Workflow with Traffic Shift Strategy
- Step 2: Add Traffic Split Step
- Step 3: Add Verification Step
- Step 4: View Verification Results
Before You Begin
- Review the prerequisites for configuring the Workflow using Traffic Split Strategy.
- Follow the deployment instructions for Blue/Green Deployment with Incremental Traffic Shift.
Step 1: Add the Workflow with Traffic Shift Strategy
Create the Blue/Green Workflow
- In the Harness Application containing the Service and Infrastructure Definition you want to use, click Workflows.
- Click Add Workflow.
- Enter a name for the Workflow.
- In Workflow Type, select Blue/Green Deployment.
- Select an Environment and Service, and the Infrastructure Definition containing your imported Elastigroup JSON Configuration.
- In Traffic Shift Strategy, select Incrementally Shift Traffic using ELB.
- Click Submit.
Harness creates the Workflow and automatically adds the steps for deployment.
By default, only one Shift Traffic Weight step is added. Unless you want to shift the traffic in one step, you will likely add more Shift Traffic Weight steps to incrementally shift traffic.
For more information about Blue/Green Deployment and Workflow creation, see Blue/Green Deployment with Incremental Traffic Shift.
Step 2: Add Traffic Split Step
- Add the required steps in sections for deployment and staging verification.
- Add traffic shift steps in the Route Update section after the Verify Staging section based on the percentage shift required.
You can manipulate traffic shifting using as many Shift Traffic Weight steps as you like.
Typically, you add Approval steps between each Shift Traffic Weight step to ensure that everything is running smoothly. For example, you can test the new feature(s) of your app before approving. This is a simple way to incorporate A/B testing into your Workflow.
Approval steps are very useful because they enable you to cancel a deployment and return to the pre-deployment traffic weighting with a single step.
Step 3: Add Verification Step
In the Route Update section, after each traffic split step, you can add the verification step for one of the following:
- Performance Monitoring—AppDynamics: For more information on configuring AppDynamics verification, see Verify Deployments with AppDynamics.
- Log Analysis—ELK: For more information on configuring ELK verification see Verify Deployments with Elasticsearch.
The configure AppDynamics/ELK procedure is similar to the regular configuration, except for the Baseline for Risk Analysis input. You can select only Canary Analysis.
Step 4: View Verification Results
Once you have executed the Workflow, Harness performs the verification you configured and displays the results in the Deployments and Continuous Verification pages. Verification is executed in real time, quantifying the business impact of every production deployment.