# Monitoring to DevOps Integration

Whether your teams use Dynatrace, Datadog, Splunk, Zabbix, New Relic, or another observability tool, ZigiOps enables real-time data exchange with DevOps platforms such as Jira, Azure DevOps, GitHub, and more.

### What Monitoring and DevOps Systems Can I Connect?

ZigiOps supports 60+ enterprise systems. Any monitoring platform with an accessible API can be integrated with any DevOps tool supported by ZigiOps.

**Monitoring and observability tools supported by ZigiOps:**

* Dynatrace
* Datadog
* Splunk Enterprise / Splunk Observability
* SolarWinds
* New Relic
* Zabbix
* Icinga
* Nagios XI
* Prometheus
* AppDynamics
* OBM / OpsBridge
* Amazon CloudWatch
* Azure Monitor
* CA UIM
* vROps
* Foglight
* SAP Solution Manager

**DevOps tools supported by ZigiOps:**

* Jira (Software and Service Management)
* Azure DevOps
* GitHub
* Bitbucket

| Monitoring Tool (examples) | DevOps Tool (examples) | Typical Scenarios                                                                    |
| -------------------------- | ---------------------- | ------------------------------------------------------------------------------------ |
| Dynatrace                  | Jira                   | Create Jira issues from Dynatrace problems; sync resolution status back to Dynatrace |
| Datadog                    | Azure DevOps           | Forward Datadog monitor alerts to Azure DevOps work items for engineering triage     |
| Splunk                     | Jira                   | Convert Splunk notable events to Jira bugs for developer follow-up                   |
| Zabbix                     | Jira                   | Create Jira issues from Zabbix triggers; close them when alerts resolve              |
| New Relic                  | Azure DevOps           | Forward New Relic violations to Azure DevOps for engineering investigation           |
| **Any monitoring tool**    | **Any DevOps tool**    | **Any alert type, any entity - configurable via ZigiOps**                            |

{% hint style="info" %}
ZigiOps can integrate with any system that exposes a REST API, even if it is not in the pre-built template library.
{% endhint %}

***

### What Data Can Be Synchronized?

ZigiOps supports synchronization of standard and custom fields, alert and event data, severity mappings, and state transitions between monitoring tools and DevOps platforms. Each field can be mapped independently per direction.

| Entity type        | Direction            | Examples                                      | Common fields synchronized                                                     |
| ------------------ | -------------------- | --------------------------------------------- | ------------------------------------------------------------------------------ |
| Alerts / Events    | Monitoring - DevOps  | Dynatrace Problem - Jira Bug                  | Node/CI, Title/Summary, Severity/Priority, Status/State, Category, Description |
| Build failures     | CI - DevOps tracking | Jenkins Build Failure - Jira Issue            | Build ID, Status, Result, Branch, Error message                                |
| Custom alert types | Both directions      | Any monitoring entity - Any DevOps issue type | All standard and custom fields supported                                       |

***

### How Does the Monitoring to DevOps Integration Work?

ZigiOps acts as a secure integration layer between monitoring and DevOps systems, using their native APIs and event mechanisms to read and write data.

* No scripting or custom development required
* All configuration is done through the ZigiOps UI
* Supports polling-based, event-driven, and webhook-based synchronization
* Start from a pre-built template or build a custom integration from scratch
* Apply severity translations, state transitions, field mappings, and filters
* Does not permanently store transferred business data

***

### Setup

Follow the steps below to enable a Monitoring to DevOps integration using ZigiOps.

1. Log in to your ZigiOps instance.
2. Navigate to **ZigiOps - Configurator**.
3. Load the desired integration template (or create a new one from scratch).
4. Select the corresponding **Integrated Systems**.
5. Click **Save** to continue.
6. Enable the integration using the **slider button** located in the middle section of the screen.

Once enabled, ZigiOps starts synchronizing data based on the configured mappings and rules.

***

### Frequently Asked Questions (FAQ)

<details>

<summary>Do I need coding or API skills to set up a custom integration?</summary>

No. All configuration is handled through the ZigiOps UI. No scripting or API expertise is required.

</details>

<details>

<summary>Can I integrate systems that do not appear in the pre-built template library?</summary>

Yes. ZigiOps allows you to create integrations from scratch for any system with an accessible API.

</details>

<details>

<summary>Is bi-directional synchronization supported?</summary>

Yes. All integration types support bi-directional data flow, configurable per field.

</details>

<details>

<summary>How does ZigiOps prevent update loops?</summary>

ZigiOps uses correlation IDs and internal deduplication logic to prevent circular updates between systems.

</details>

<details>

<summary>Can I apply conditions and filters to control which records are synchronized?</summary>

Yes. Conditions, filters, and transformations can be applied at the field, record, or workflow level.

</details>

<details>

<summary>Does ZigiOps store transferred business data?</summary>

No. ZigiOps does not permanently store transferred business data.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zigiwave.com/integration-catalog/monitoring-to-devops-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.