FAQ

Please, do not hesitate and contact us, we are happy to show you how this integration works, and if you are interested, we will provide you time-limited trial license, to test it in your environment!

After you contact us, we can provide you with the latest build of Jira plugin and the license to make it work.

Please, do not hesitate and contact us, we are happy to show you how this integration works, and if you are interested, we will provide you time-limited trial, to test it in your environment!

This is a commercial application with a subscription license.

We are aware that seeing the integration in action with your own data gives you better insight into how it works and how can you benefit from that and therefore yes, we can also provide the trial, time limited, license

The only required action in Dynatrace is to create an API token with proper permissions, so the problem and topology data can be pulled fromDynatrace to Jira.

If you are interested in problem synchronization, you will also need to setup new custom notification integration and for some advanced options you might want to consider setting up notification profiles or management zones to filter which entities are going to be synchronized into Jira and which not. More information about the application setup: Installation

Yes! Problem synchronization and Smartscape topology import are two areas, that even though work very well together, are also functional independently.

If you decide not to use Insight CMDB, Dynatrace entities affected by the problem could still be presented on issues as labels.

Yes! Problem synchronization and Smartscape topology import are two areas, that even though work very well together, are also functional independently.

If you do not want to use problem synchnonization, you can turn it of in add-on settings and skip the notification setup on Dynatrace side.

Of course! If it makes no sesnse for you to import whole infrastructure, you can set up filter based on Dynatrace features like Management Zones or you can filter entities on Jira side with IQL which is native query languare for Insight CMDB.

Predefined structure is a complete structure we prepared for you to give you a quick start and an idea of what data you can get from Dynatrace entities and what you can do with it.

Structure can be modified to your own preference as well as the attribute mapping. You can use all the features Insight as a CMDB provides.

This can happen with the select type attributes with wrong setting of Unknown Values in schema configuration. Predefined schema is not creating options by itself as these lists can be extended whenever Dynatrace makes update to its API. We rely on these API values and option should be added each time a new value has been discovered. Therefore the proper setting for Unknown Values is ADD.

Missing objects can be handled with Insight OOTB functionality. From Jira side is missing object every entity that was not returned by API. You can do three things with those entities:

• ignore - does nothing, objects stay in CMDB unchanged

• delete - object is deleted, history is lost and other objects that referenced to this object will lose the reference

• update - allows you to update one of the entity (CI) attributes which can serve as a flag of the object no longer available through API

Update option can be used to set e.g OOTB Last Seen attribute or newly created Status attribute. It has to be set up in each CI type where you want the automation to perform the action.

Note: Threshold setting can be used to set minimum number of days or imports when object has to be missing for automation to edit this attribute. It can be used when it happens often in your environment that e.g. host can be disconnected for a while but you don’t want to update it as inactive on the first import - just after some time passes.

Sure thing!

First off, you have to decide what type of data you want to store and create a proper attribute type for this kind of information. You can choose from text, email, list with options, status, URL or IP and name the attribute whatever you like. After creating the attribute, it is not directly visible on CI detail page as only attributes with value are being displayed. When you click the edit option, it should be now accessible from that screen and can be filled with a value.

Note: Remember to use custom data with proper Missing Objects import configuration policy (Ignore or Update) so the data won’t get deleted after it is no longer avalable through the Dynatrace API - unless you want it to. With this setup also after the entity is no longer monitored, data stays in your CMDB as long as it does not get manually deleted by a user.

Quick answer would be

• Auto CMDB sync

• Auto ticketing with business impact and root cause

• Link technical problems to business processes

• Auto problem remediation…

But we at TEMPEST with over 25 years of experience in ICT management know, that it does not end with just clicking on Import button. There is plenty of things you can do with this integration but it is really customer specific and requires the vision or goal you want to get to and we can help you with the process of analysis, design and implementation to reach that goal.

This integration is developed and maintained by TEMPEST, Master Dynatrace Partner for Slovakia and Czech Republic and Atlassian Gold Solution Partner.

We have a team with over 25 years of experience in ICT management and monitoring, and currently, we have 4 global certified Atlassian individuals, 5 certified Dynatrace professionals and 7 certified Dynatrace associates.

If you have any Dynatrace, Jira, monitoring or service management related questions, give it a shot and contact us, our team is ready to help you.