xMatters - OpsBridge Integration
Connect xMatters and Micro Focus OpsBridge in a few clicks and automate the data exchange between your teams and departments.
Data Types: Events / Updates (status and comments)
xMatters (Event) → OBM (Event)
OpBridge - xMatters Integration Use Case
With ZigiOps, you can easily sync your ITOM, DevOps and SRE teams by connecting xMatters and Micro Focus OpsBridge.
OpsBridge receives events from different tools, which you can redirect automatically (based on specific conditions) to xMatters with ZigiOps. The opposite is also possible, as this integration is bi-directional.
OBM receives a new Event in the Event browser. ZigiOps detects it and creates a new alert in xMatters, featuring all the OBM event details.
You have granular field mapping control where you can set trigger conditions based on your use case, and define which updates get transferred between the two tools. Updates include lifecycle synchronization, regular fields, custom attributes, and annotations.
You can also sync Active or Closed Events from xMatters to OpsBridge. Again, you can define your custom fields in the field map, and update Events back bi-directionally. You can also take a custom field from OpsBridge and report it as a comment in xMatters.
Challenges for xMatters and OpsBridge users
xMatters is a popular solution that helps your teams guarantee continuous uptime and availability. OpsBridge allows Operations and Monitoring teams to have a quick birdseye overview of the health and performance of all resources.
If your company is using both tools without synchronizing them, you risk creating confusion and misalignment between teams. Manually transferring events and incidents between the two can result in errors, duplicate records, or delay resolution of problems. Seamless end-to-end data flow is a must for teams to be efficient.
How do we solve them?
With ZigiOps, you get out-of-the-box, fully customizable templates, which allow you to integrate xMatters and OpsBridge in a few clicks. The integration is bi-directional and keeps both systems updated in real time. You get a wide set of actions, conditions, and transformations that help you adjust for your specific use case.
This allows you to eliminate human errors and duplicated tasks, and act fast to solve any issues as they arise.
• Transform Azure tasks to Jira tasks based on the mapping
• Create new Jira task in ZigiOps
• Transform Jira task updates to the Azure task based on the mapping
• Update the corresponding Azure task based on the mapping
• Add comment to the Azure task for the new comment of the Jira task if any
• Transform Azure task updates to the Jira task based on the mapping
• Update the corresponding Jira task based on the mapping
• Add Comment to the Jira task for the new comment of the Azure task if any
Related resource:
Request
Didn’t find the integration you were looking for? Fill in the form below to request an integration: