Integrate with Dynatrace AppMon

If you’re a customer who shifted your operations from Opsgenie to Jira Service Management, adding new instances of this integration isn’t possible in Jira Service Management. You can only edit the integrations that originally shifted from Opsgenie.

What does Jira Service Management offer to Dynatrace AppMon users?

Jira Service Management provides a powerful bidirectional integration with Dynatrace AppMon. When a new incident is created in Dynatrace AppMon, a corresponding Jira Service Management alert is automatically created, containing rich information about the incident. Jira Service Management provides rich notifications with on-call rotations, scheduling features, and alert escalations to ensure the best incident management for Dynatrace AppMon customers.

Functionality of the integration

When an incident is created in Dynatrace AppMon, it creates an alert in Jira Service Management.
When an incident is closed in Dynatrace AppMonn, the related alert is closed in Jira Service Management automatically.
If Send Alert Updates Back to Dynatrace AppMon is enabled, actions for Dynatrace AppMon is executed in Dynatrace AppMon when the chosen action is executed in Jira Service Management for alerts which are created by the Dynatrace AppMon integration.

Edit Dynatrace AppMon integration in Jira Service Management

To edit a Dynatrace AppMon integration in Jira Service Management, complete the following steps:

Go to your team’s operations page.
On the left navigation panel, select Integrations.
Search for your Dynatrace AppMon integration.
Edit the integration settings and rules as necessary.

Use the instructions in the following sections if applicable.

Configure the integration in Dynatrace AppMon

First, download the Dynatrace AppMon Plugin.
Go to Dynatrace Client and select Manage Plugins from the Tools menu.

3. Then, click Install Plugin in the opening window.

4. Select the Plugin JAR downloaded previously and click Open.

5. Then, select Opsgenie Plugin from the listed plugins and click Properties.

6. Paste the integration URL copied previously to the Webhook URL field in the opening Plugin Properties window. This field is configured during Edit Incident Rule to use different integrations.

7. Enter the team names that exist in Jira Service Management so that alerts can be created in Jira Service Management for those specific teams only. This field can be kept empty and configured during Edit Incident Rule in order to assign different alerts to different teams in Jira Service Management.

Dynatrace AppMon configure plugin properties

8. Click OK, then access Incidents from left side menu.

9. From Incidents, select the incident to use for Jira Service Management alerts and choose Edit Incident Rule from the dropdown menu.

10. Click Advanced Configuration on the Actions tab.

Dynatrace AppMon advanced configuration actions tab

11. Then click Add.

12. Select Dynatrace Plugin from the listed plugins and click Add. Fields in Properties part to be configured here in order to use different integration or assign alerts to different teams in Jira Service Management.

13. Choose "on incident begin" as Execution option and click OK.

Integration via OEC

Alternatively, use Jira Service Management's JEC and the Dynatrace AppMon script to execute actions on Dynatrace AppMon. This enables deployment of your own scripts/ability to modify the ones provided and execute customized actions on Dynatrace AppMon.

To use the Dynatrace AppMon integration package, follow the steps in the sections below through the end.

Download the latest version of OEC

To download the latest version of Dynatrace AppMon package, please use readme file of oec-scripts repository.

Installation

For Red Hat Based Distributions

Run following command : rpm -i opsgenie-dynatraceappmon-<your_version>.rpm

For Debian Based Distributions

Run following command : dpkg -i opsgenie-dynatraceappmon-<your_version>.deb

For Windows

Unzip opsgenie integration zip file which contains OEC package into a directory (C:\opsgenie\oec is the preferred path.)

For convenience lets refer to this Unzip path as %OEC_HOME%, you can create a system environment variable called OEC_HOME with the value of the unzip location, to do this open an elevated Powershell session and enter this command:

Text

[Environment]::SetEnvironmentVariable("OEC_HOME", <Path where you extracted OEC package>, 'Machine')

In order to learn more about how to run OEC you can refer to the Running OEC documentation.

Configuring Dynatrace AppMon Integration for OEC

In order to use OEC utility, enable Send Via OEC.
Other configurations regarding Dynatrace AppMon can be done either via integration page or OEC configuration file config.json. The configuration via the integration page precedes the configuration file.

OEC Configuration

To be able to execute actions in Dynatrace AppMon, OEC gets the configuration parameters from the configuration file /home/opsgenie/oec/conf/config.json (Linux) or %OEC_HOME%\conf\config.json (Windows).

Configuration parameters

apiKey – Copy the API key from the Dynatrace AppMon integration created above.
userName – Dynatrace AppMon username.
password – Password for Dynatrace AppMon users.
url – Dynatrace AppMon url where actions are sent to (ex:https://localhost:8021).
profileName – The name of the corresponding System Profile.

The package that you downloaded also includes OEC utility which is located at path /usr/local/bin/OpsgenieEdgeConnector (Linux) or %OEC_HOME%\OpsgenieEdgeConnector.exe (Windows) and the script that is needed to be run by OEC which is under /home/opsgenie/oec/scripts/actionExecutor.py (Linux) or %OEC_HOME%\scripts\actionExecutor.py (Windows). After the configuration of OEC is done, you need to run it. In order to learn more about how to run OEC, you can refer to the Running OEC documentation.

Dynatrace AppMon Configurations

Go to the Dynatrace Server and select Users from left menu.

2. From the Users window, select the role of the user.

3. Check the permissions of this user role and add Analyze Incidents, Manage Incidents and Web Service Interface Access if the user role doesn't have these.

Sample parameters sent to OEC

JSON

{
   "type":"DynatraceAppMon",
   "alertId":"0e321daf-6532-4277-a61c-83d90dea9969",
   "customerId":"d17aae0e-7730-4788-bbd5-a306816287d3",
   "action":"Acknowledge",
   "mappedActionV2":
    {
      "name":"inProgressIncident",
      "extraField":""
    },
    "integrationId":"2bdcf8c9-a423-4efd-957c-07ee7de236ea",
    "integrationName":"Dynatrace AppMon",
    "integrationType":"DynatraceAppMon",
    "sendViaOEC":true,
    "profileName":"",
    "incidentRule":"",
    "userName":"",
    "password":"",
    "url":"",
    "state":"InProgress",
    "alias":"b324f7e2-c747-47bb-83d5-17b6a8eafaf8"
}

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community