Use Case

Learn more about the integration template's use case.

  • Collect problems from Dynatrace to create events in OBM
  • Receive problems from Dynatrace to create events in OBM (optional alternative)

Requirements

Learn more about the integration template's requirements.

Product Requirements

Learn more about the integration's requirements.


DynatraceOperations Connector

Authentication

  • API Token

  • N/A

Permissions

  • Access problem and event feed, metrics, and topology
  • Read Entities
  • Read Problems
  • Read Metrics
  • N/A

Network Requirements

Learn more about the network's requirements.


Workflow Direction (Port)
Communication
  • ZigiOps → Dynatrace (80/443)
  • ZigiOps → Operations Connector (30005)
  • Dynatrace → ZigiOps (9094) [OPTIONAL]

Environmental Prerequisites

Learn more about the environmental prerequisites.

Dynatrace

Note that creating a Dynatrace problem notification is an optional prerequisite.

  1. Access the Dynatrace web console.
  2. Go to Settings > Integration > Problem Notifications > Custom Integration and configure the following settings:
    • Name → This is the display name of the problem notification.
    • Webhook URL → This is the URL of the ZigiOps listener. For example, https://zigiops.example.com:9094/listener/dynatracesaas/problem.
      • It is mandatory to enable the Accept any SSL certificate (Self signed or invalid) option.
    • Custom Payload → This is the payload that Dynatrace sends to the ZigiOps listener. It's mandatory to use the code below.

      {
          "problem_title": "{ProblemTitle}",
          "problem_details": "{ProblemDetailsText}",
          "status": "{State}",
          "severitylevel": "{ProblemSeverity}",
          "impactlevel": "{ProblemImpact}",
          "rankedimpacts": {ImpactedEntities},
          "tagsofaffectedentities": "{Tags}",
          "problem_url": "{ProblemURL}",
          "id": "{PID}"
      }
      CODE
  3. Click the Send test notification button.
  4. Click the Save button.

Operations Connector

  1. Download the ZigiOps Policies Content Pack from https://download.zigiwave.com/zigiops/contentpacks/obm_cp_zigiops_policies_1.00.zip.
  2. Access your OBM instance and login with a user who has sufficient administrative permissions.
  3. Go to Administration > Setup and Maintenance > Content Packs, click the Import button, and select the content pack file.
  4. Go to Administration > Monitoring > Policy Templates, select the ZigiOps Policies template group, select one of the policies, and click the Assign & Deploy button.
  5. Select the desired instance(s) and click the Assign button to finalize the operation.

Repeat Step 4 and Step 5 to import the remaining policies.

Setup

Learn more about how to set up the integration template.

  1. Access the platform's web console.
  2. Go to the Configurator menu.
  3. Load the Dynatrace problems to OBM events (OA) integration template.
  4. Select the Integrated Systems and the Integrated Entities from the drop-down menus.
  5. Press the Save button to save the changes.
  6. Enable the integration from the Slider button.

Actions

Learn more about the integration template's actions.

Create Open Event (POLLING)

This action sends HTTP requests on a scheduled interval to collect open problems from Dynatrace to create events in OBM.

Source

You could customize the trigger type, trigger conditions, and expressions or use the defaults from this tab.

Field Map

You could customize the field, value, and conditional mappings that suit your requirements or use the defaults from this tab.

Create Closed Event (POLLING)

This action sends HTTP requests on a scheduled interval to collect closed problems from Dynatrace to create events in OBM.

Source

You could customize the trigger type, trigger conditions, and expressions or use the defaults from this tab.

Field Map

You could customize the field, value, and conditional mappings that suit your requirements or use the defaults from this tab.

Create Event (LISTENER)

This is an optional action that registers a web service listener on the ZigiOps host, which listens on a specific port and path. It is designed to accept the incoming requests sent by Dynatrace. When Dynatrace detects a new problem, it will send a request to the ZigiOps listener. The ZigiOps accepts the request, then it is internally processed through the field mapping configuration, and finally, a request is sent to OA to report the new event.

Source

You could customize the trigger type, trigger conditions, and expressions or use the defaults from this tab.

Field Map

You could customize the field, value, and conditional mappings that suit your requirements or use the defaults from this tab.