header background

Technical review: Dynatrace and Micro Focus OpsBridge integration through ZigiOps


Many OpsBridge users count on Dynatrace for monitoring some fragments of their environment together with the native Micro Focus data collectors and other tools. In order to improve their overall visibility and reduce the number and duration of outages, there is a variety of measures to be taken.

By far the most recognized one is combining all the data sources into a single console where it can be processed accordingly. This is why a good integration between Dynatrace and OpsBridge is extremely important.

ZigiOps also allows other Dynatrace integrations – with ServiceNow, JIRA, BMC Remedy, and more.



Only a few simple steps are needed to configure the Dynatrace and OpsBridge integration through ZigiOps:

  • Install ZigiOps
  • Connect to Dynatrace and OpsBridge.
  • Configure the topology, metrics and problems polling intervals (each one of them is independent and can be configured separately).
  • Activate the integration.

More information can be found here.


ZigiOps can replicate the Smartscape Topology from Dynatrace into the Ops Bridge RTSM (or directly into UCMDB) according to all the Micro Focus standards and best practices.

However, the Configuration items (CIs) can always be modified according to the customer requirements – the CI type can be changed, new attributes can be added or existing ones can be removed.

Smartscape topology in Dynatrace and Ops Bridge topology created by ZigiOps:


Default mappings*:


*all mappings can be changed by the customer


Any metric collected by Dynatrace can be extracted by ZigiOps and loaded to Ops Connector DB (accessible through the Performance Perspective), a file on the file system or COSO (coming soon). Metric filtering is user configurable and is done through the ZigiOps UI.

Apdex in Dynatrace and Apdex in Ops Bridge Performance Perspective:



New Dynatrace problems (or events) can create new events in OpsBridge. All the necessary attributes for an event to be meaningful are present:

  • Title containing the Problem # in Dynatrace
  • Severity
  • Related CI (can be one of application, host, service or process)
  • Description
  • Drill-down URL to the original Dynatrace problem
  • Other custom attributes

Dynatrace Problems can also trigger new incidents in ServiceNow, BMC Remedy, Cherwell, JIRA Service Desk or any kind of issue in JIRA.

Problem in Dynatrace and Event in OpsBridge:


ZigiWave at Dynatrace Partner space – here.

Ops Bridge and ServiceNow integration