3 - Verify Deployments with Dynatrace
The following procedure describes how to add Dynatrace as a verification step in a Harness workflow. For more information about workflows, see Add a Workflow.
Once you run a deployment and Dynatrace preforms verification, Harness' machine-learning verification analysis will assess the risk level of the deployment.
Deployment Verification Setup
To verify your deployment with Dynatrace, do the following:
- Ensure that you have added Dynatrace as a verification provider, as described above.
- In your workflow, under Verify Service, click Add Verification, and then click Dynatrace. The Dynatrace dialog appears.
The Dynatrace dialog has the following fields.
This dropdown contains the names of the Dynatrace verification providers you added, as described above.Select the name of the Dynatrace verification provider that connects to the Dynatrace environment associated with the microservice/application this workflow deploys.
Enter the SERVICE_METHOD IDs of your key transactions. These are the service methods (key business transactions) you want to verify in addition to a verification time period (the default is 15 minutes).
The transactions must be marked as key transactions in Dynatrace because the Dynatrace API supports fetching of data only if a transaction is marked as a key request.
Harness is working with Dynatrace to update their API so you can just select an application or service name and it will automatically verify all key business transactions associated by default.
To find the SERVICE_METHOD ID of a transaction, do the following:
Analysis Time duration
Set the duration for the verification step. If a verification step exceeds the value, the workflow Failure Strategy is triggered. For example, if the Failure Strategy is Ignore, then the verification state is marked Failed but the workflow execution continues.
Baseline for Risk Analysis
When you are finished, click SUBMIT. The Dynatrace verification step is added to your workflow.
Once you have deployed your workflow (or pipeline) using the Dynatrace verification step, you can automatically verify cloud application and infrastructure performance across your deployment. For more information, see Add a Workflow and Add a Pipeline.
To see the results of Harness machine-learning evaluation of your Dynatrace verification, in your workflow or pipeline deployment you can expand the Verify Service step and then click the Dynatrace step.
You can also see the evaluation in the Continuous Verification dashboard. The workflow verification view is for the DevOps user who developed the workflow. The Continuous Verification dashboard is where all future deployments are displayed for developers and others interested in deployment analysis.
To learn about the verification analysis features, see the following sections.
Deployment infoSee the verification analysis for each deployment, with information on its service, environment, pipeline, and workflows.
Verification phases and providersSee the vertfication phases for each vertfication provider. Click each provider for logs and analysis.
Verification timelineSee when each deployment and verification was performed.
Execution detailsSee the details of verification execution. Total is the total time the verification step took, and Analysis duration is how long the analysis took.
Risk level analysisGet an overall risk level and view the cluster chart to see events.
Transaction-level summarySee a summary of each transaction with the query string, error values comparison, and a risk analysis summary.
Event typeFilter cluster chart events by Unknown Event, Unexpected Frequency, Anticipated Event, Baseline Event, and Ignore Event.
Cluster chartView the chart to see how the selected event contrast. Click each event to see its log details.
Event-level analysisSee the threat level for each event captured.
Tune event captureRemove events from analysis at the service, workflow, execution, or overall level.
Event distributionClick the chart icon to see an event distribution including the measured data, baseline data, and event frequency.