Original Developer: Abel Wang (Microsoft) Maintainer: Dynatrace Innovation Lab (Main contact: @grabnerandi)

Special thanks goes to Abel Wang and Donovan Brown who started implementing this plugin. More details on Abels blog about The Dynatrace Unbreakable Pipeline in VSTS and Azure

Disclaimer The Dynatrace Unbreakable Pipeline for VSTS plugin is currently in Early Access. Early Access releases provide early-stage insight into new features and functionality of the Dynatrace Platform. They enable you to provide feedback that can significantly impact our direction and implementation.

While Early Access releases aren't ready to be used to build production solutions, they're at a stage where you can test and tinker with an implementation. As we receive feedback and iterate on a project, we anticipate breaking changes without advanced warning, so Early Access releases should not be used in a user-facing manner or applied to production environments.

The Dynatrace Unbreakable Pipeline for VSTS consists of the following use case:

• monitor your app in all the environments using Dynatrace
• use monspec files to define what you want to monitor and your performance thresholds
• use Dynatrace Unbreakable Pipeline Release Gate to automate the approval between environments based on performance data captured while running continuous performance tests after a release.
• self healing after deploying into production via rollback to previous release if problems detected with Dynatrace

To implement the Unbreakable Pipeline, you will need the Dynatrace Unbreakable Pipeline VSTS extension. This extension consists of two things

• Dynatrace Unbreakable Pipeline Release Gate
• Dynatrace Push Deployment Event Task

You can find the code for the extension here.

The release gate uses an Azure function for a serverless on-demand processing of performance data captured while running performance tests during a release. The code for this function is here.

The release gate also uses a proxy which consists of a VM with python installed and the Dynatrace CLI. The proxy code uses the Dynatrace CLI to pull monspec info from Dynatrace.

The code for the proxy is here.

Need to make this into a container. Would be super cool to have this deployed in Azure Container Instance and have the gate launch this.

Self healing web hook uses an Azure function for a serverless on-demand processing and rollback of releases. The code for the self healing azure function is here.

Input into the self healing webhook/function is in the form:

{
    "State":"{State}",
    "ProblemID":"{ProblemID}",
    "ProblemTitle":"{ProblemTitle}",
    "PID": "{PID}",
    "ImpactedEntities": {ImpactedEntities}
}

Currently setup is all done manually. Would be cool to use Donovan's Yo Team to scaffold out the entire pipeline for a project.