Dynatrace JIRA Cloud Connect Add-On
The Dynatrace JIRA Cloud Connect Add-On enables several Use-Cases for JIRA Cloud
- Live Dynatrace Problem Status and Problem Events in JIRA ticket
- Automatically link JIRA tickets with Dynatrace Problems
- Synchronize JIRA ticket comments with Dynatrace Problems
- Direct links to root cause dashboards from your JIRA ticket
- Enable JQL queries based on Dynatrace Problem data: severity, impact, tags, ...
- Query Dynatrace metrics from your JIRA ticket
Want to see the Add-On in action? Watch this video Want to learn more about our learnings when we implemented this Add-On? Read our Atlassian Connect blog Want to see the HipChat Add-On we built? Dynatrace HipChat Add-On on GitHub
Getting started with this Add-On
In order to use this integration you need
- A Dynatrace FullStack instance (Managed or SaaS): Get your own Dynatrace SaaS Trial in 3 minutes
- A Dynatrace API Token: In Dynatrace go to Settings -> Integration -> Dynatrace API and create a new token
- A JIRA cloud instance: Get your JIRA Cloud instance
- (optionally but recommended). Configure the Dynatrace to JIRA Integration.
In your JIRA instance navigate to "Managed Add-Ons". As we haven't published the Add-On on the Atlassian Marketplace yet simply follow these steps
- Click on "Upload add-on"
- Enter: https://atlassian-connect.dynatracelabs.com/atlassian-connect.json
- Once the Add-On is installed click on "Configure"
- Enter your Dynatrace Tenant URL as well as a Dynatrace API token.
Self-Hosting of Dynatrace Add-On?
If you run JIRA or Dynatrace On-Premises and cannot connect to our hosted instance feel free to host the plugin yourself. Our plugin is implemented in Node.js and is therefore easy to host. It should only take these steps:
npm install node app.js
In JIRA navigate to "Managed Add-Ons". Click on "Upload add-on" and specify the URL to your hosted Add-on, e.g: http://yourserver:PORT/atlassian-connectjson
Key Use Cases explained!
For more details on each use case we recommend to read our Atlassian Connect Week Austin 2017 blog where we explained the technical implementation of the following use cases:
Linking a JIRA ticket with a Dynatrace Problem
The linkage between a JIRA ticket and a Dynatrace Problem is done by storing the Dynatrace Problem ID as an Entity Property on the JIRA ticket. The property is named "dynatraceProblemId" and contains a JSON object with details such as "Unique Dynatrace Problem ID", "Severity", "Impact", "Tags", "Status". The property itself is not visible to the end user. End users can however use JQL (JIRA Query Language) to search for JIRA tickets that are associated with a Dynatrace Problem. The "dynatraceProblemId" entity property is set in different scenarios
- Our Dynatrace to JIRA Integration will create JIRA tickets and automatically set this property.
- 3rd party tools such as xMatters set this property when forwarding a Dynatrace Problem to JIRA
- Our JIRA Add-On scans and parses links to Dynatrace Problem URLs in JIRA ticket descriptiosn and comments. If detected the entity property is stored.
Live Problem Status Overview
Live Problem Events Feed
The Dynatrace Events tab automatically pulls in all comments and correlated problem events from the linked Dynatrace Problem. The list highlights special events and provides direct links to Dynatrace root cause dashboards
The linked Dynatrace problem data including Tags, Impact, Severity, Status, ... is indexed by JIRA. This allows JIRA users to query JIRA tickets that are linked to Dynatrace Problems. This is especially useful to search for related problems.
If you add a comment to a JIRA ticket we do not only scan for a link to a Dynatrace Problem to link the ticket with that problem. In case the JIRA ticket is already linked we push the comment to the Dynatrace side so that the comment can be seen in both JIRA and Dynatrace.
Query Dynatrace metrics
As a JIRA user you can execute a query against Dynatrace to pull LIVE metrics for certain entites, e.g: Number of Active Users on the website or Response Time of a service. This allows you to close the Feedback Loop from Operations & Testing back into your development team.
Give us feedback on further extensions to the Add-On. Which use cases are missing? Would you also like to see tighther integrations with other Atlassian tools?