You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Currently we are using integration between OpsGenie and Jira SD via Opsgenie Edge Connector (OEC). We had to do it that way so we could work with priorities and tags/components.
Now there is plan to migrate to Jira Cloud so I would like to ask how we can continue using OEC so we could manage priorities and tags. We are also using tags to filter alerts which will get to Jira.
So basically I would like to know is handled functionality of OEC for OpsGenie/Jira Cloud integration.
Hi @pavol_cvincek01 ,
You can continue to use OEC after the migration. Although OEC is primarily used for on-prem instances, we do see customers using it with their cloud instances to map Opsgenie alert fields to specific Jira / JSM issue fields.
We also recently released a new Jira and JSM integration framework that can map these fields - including some custom fields - out of the box without using OEC: https://community.atlassian.com/t5/Opsgenie-articles/NEW-Jira-Software-and-Jira-Service-Management-Opsgenie/ba-p/1952529
Hello @Nick H ,
It's great that you are taking care of those priorities. That's what we missed back then, together with tags/components. I have spent a lot of time with coding of the python script to make priorities and tags/components work for us.
So in case we would like to continue use OEC even for Jira Cloud what would be the solution?
Would be enough to update "/home/opsgenie/oec/conf/config.json" for oec.service? Currently we have Red Hat VM where Jira SD and OEC resides so after the migration to Jira Cloud, only OEC would remain and took care of the integration from OpsGenie to Cloud Jira.
Is that it or there is more to make it work?