Dynatrace AppMon Integration

Dynatrace AppMon provides deep application monitoring and performance lifecycle management.

What does Opsgenie offer to Dynatrace AppMon users?

Opsgenie provides a powerful bidirectional integration with Dynatrace AppMon. When a new incident is created in Dynatrace AppMon, a corresponding Opsgenie alert is automatically created, containing rich information about the incident. Opsgenie 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 Opsgenie.
  • When an incident is closed in Dynatrace AppMon, the related alert is closed in Opsgenie 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 OpsGenie for alerts which are created by the Dynatrace AppMon integration.

Add Dynatrace AppMon Integration in Opsgenie

  1. Please create an Opsgenie account if you haven't done so already.
  2. Go to Opsgenie's Dynatrace AppMon Integration page.


For Free and Essentials plans, you can only add the integrations from the Team Dashboards, please use the alternative instructions given below to add this integration.

  1. Specify who is notified of Dynatrace AppMon alerts using the Teams field. Autocomplete suggestions are provided as you type.


An alternative for Step 2) and Step 3) is to add the integration from the Team Dashboard of the team which will own the integration. To add an integration directly to a team, navigate to the Team Dashboard and open Integrations tab. Click Add Integration and select the integration that you would like to add.

  1. Copy the integration URL to use during Dynatrace AppMon Plugin configuration.
  2. Click Save Integration.

Configuration in Dynatrace AppMon

  1. First, download the Opsgenie Dynatrace AppMon Plugin.
  2. Go to Dynatrace Client and select Manage Plugins from the Tools menu.
  1. Then, click Install Plugin in the opening window.
  1. Select Opsgenie Plugin JAR downloaded previously and click Open.
  1. Then, select Opsgenie Plugin from the listed plugins and click Properties.
  1. 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.
  2. Enter the team names that exist in Opsgenie so that alerts can be created in Opsgenie 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 Opsgenie.
  1. Click OK, then access Incidents from left side menu.
  1. From Incidents, select the incident to use for Opsgenie alerts and choose Edit Incident Rule from the dropdown menu.
  1. Click Advanced Configuration on the Actions tab.
  1. Then click Add.
  1. Select Dynatrace Opsgenie 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 Opsgenie.
  1. Choose "on incident begin" as Execution option and click OK.

Integration via OEC

Alternatively, use Opsgenie's OEC 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 Utility

For Red Hat Based Distributions


For rhel6 distributions, you can download this package.

For Debian Based Distributions

For Windows

  • Download Opsgenie Dynatrace AppMon.
  • 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:

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

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


Mandatory to fill


Copy the API key from the Dynatrace AppMon integration created above



Dynatrace AppMon username



Password for Dynatrace AppMon users



Dynatrace AppMon url where actions are sent to (ex:https://localhost:8021)



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

  1. Go to the Dynatrace Server and select Users from left menu.
  1. From the Users window, select the role of the user.
  1. 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

    "integrationName":"Dynatrace AppMon",

Updated 5 months ago

Dynatrace AppMon Integration

Dynatrace AppMon provides deep application monitoring and performance lifecycle management.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.