Dynatrace Verification Overview

Updated 4 months ago by Michael Cretzman

This guide describes how to set up Harness Continuous Verification features and monitor your deployments and production applications using its unsupervised machine-learning functionality on Dynatrace.

Walk through this guide in the following order:

  1. Dynatrace Connection Setup
  2. Verify Deployments with Dynatrace

Integration Overview

Dynatrace provides constant monitoring of your application to manage performance and availability, and to provide diagnosis of performance problems and allow optimization across your stack. You can add a Dynatrace verification step to your workflow and Dynatrace will be used by Harness to verify the performance and quality of your deployments.

With Dynatrace integration, Harness can deploy and verify the performance of artifacts instantly in every environment. When a new artifact is deployed, Harness automatically connects to Dynatrace and starts analyzing the application/service performance data to understand the real business impact of each deployment.

Harness applies unsupervised machine learning (Hidden Markov models and Symbolic Aggregate Representation) to understand whether performance deviated for key business transactions and flags performance regressions accordingly.

Analysis with Dynatrace

Harness Analysis

Setup Overview

You set up Dynatrace and Harness in the following way:

  1. Using Dynatrace, you monitor your microservice or application.
  2. In Harness, you connect Harness to the Dynatrace API, adding Dynatrace as a Harness Verification Provider.
  3. After you have built and run a successful deployment of your microservice or application in Harness, you then add Dynatrace verification steps to your Harness deployment workflow.
  4. Harness uses Dynatrace to verify your future microservice/application deployments.
  5. Harness Continuous Verification uses unsupervised machine-learning to analyze your deployments and Dynatrace analytics/logs, discovering events that might be causing your deployments to fail. Then you can use this information to improve your deployments.

Next Step


How did we do?