dt-demos/pipeline-common-scripts

This repo contains reference scripts for use integrating Dynatrace into software delivery pipelines using the Dynatrace Events API

Summary

This repo contains reference scripts for use integrating Dynatrace into software delivery pipelines.

Please share feedback and your examples with a Pull Request or to me @ [email protected]

Events

In just a few steps, you can add Dynatrace Events API for things like deployments, performance tests, or configuration changes. In doing so, your development and operations teams have additional context information during review and analysis of your applications.

Read more in my Dynatrace blog

Scripts

PowerShell

• azureDevopsCaptureStartTime.ps1 - save current time to environment variable
• azureDevopsCaptureEndTime.ps1 - save current time to environment variable
• azureDevopsCustomEvent.ps1 - add Dynatrace CUSTOM_INFO event
• azureDevopsDeploymentEvent.ps1 - add Dynatrace CUSTOM_DEPLOYMENT event

Unix Shell

• bitbucketPushEvent.sh - push events from one script. Used bitbucket built-in vars for various properties in the event
• dynatrace-deployment-event.sh - add Dynatrace CUSTOM_DEPLOYMENT event
• dynatrace-push-event.sh - add misc events from on script. Modify for your CI/CD tool
• test-keptn-quality-gate.sh - used to test [http://keptn.sh](Keptn Quality Gate)
• send-traffic.sh - simple script to send load with request attributes
• wait-till-ready.sh - simply script to add after a deployment event

Local testing

In the testing/ folder are a few "wrapper" scripts that can be used to test these scripts. Just make a copy of the template file. You can update with your testing input. If you keep the prefix of test, the .gitinore file will ensure you dont check in any secrets.

pipeline-common-scripts's Issues

Tag values not found despite service being tagged

I tried to execute the script azureDevopsDeploymentEvent , ended up with the below error.

Invoke-RestMethod : {"error":{"code":400,"message":"Invalid attachRules object
2020-04-20T08:01:58.2086317Z ##[error]PowerShell exited with code '1'.
2020-04-20T08:01:58.2096445Z provided. No MEIdentifier do match: Matching rule:
2020-04-20T08:01:58.2115242Z PushEventAttachRules{entityIds=null, tagRules=[TagMatchRule{meTypes=[SERVICE],
2020-04-20T08:01:58.2115339Z tags=[[CONTEXTLESS]environment:dynatrace, [CONTEXTLESS]service:approvals]}]}"}}

I have tagged the service appropriately attached is the screengrab of the service .

Scripts outdated causing issues with tokens

I noticed that the scripts are a bit outdated as it doesn’t refer in all scripts to the events v2 but to the V1 causing issues with the required token scope according to the Dynatrace documentation. Some of the scripts have been modified but some not. Perhaps a good idea to update all of them and create a new branch?

Kind regards,

Daan

Start and end times not matching up with Dynatrace event times

The following time formats didn't work for me:

pipeline-common-scripts/captureStartTime.ps1

Line 5 in 94927a4

$startTime = Get-Date -UFormat %s

pipeline-common-scripts/captureEndTime.ps1

Line 5 in 94927a4

$endTime = Get-Date -UFormat %s

Here is what worked for me: [DateTimeOffset]::Now.ToUnixTimeSeconds()

Notes
*The difference between what Get-Date -UFormat %s and what [DateTimeOffset]::Now.ToUnixTimeSeconds() return is 21600 seconds
*The issue may be that I was running on a Windows based build agent and/or there is something up with the GMT offset