Impact of Opsgenie Retirement on Elastic Connector Configuration

[Guneycan Sanli]

I currently use Elastic rules with the Opsgenie connector (configured using the Opsgenie URL and API key) to automatically create and resolve alerts. With the upcoming retirement of Opsgenie and migration to Jira Service Management, will this functionality continue to work as it does today? Will the Opsgenie URL, API key, or connector configuration need to change, and are there any specific steps or considerations I should be aware of during the migration?

[Alexander Nilsson · Accepted solution]

Hello Guneycan, 

In the short term, your Elastic rules using the Opsgenie connector (Opsgenie URL + API key) will continue to work while Opsgenie is still active for your tenant. The integration isn’t cut off immediately just because you start the migration.

However, once you migrate to Jira Service Management Operations, the endpoints change. The Opsgenie REST API is not the long‑term target anymore, and you will need to:

- Create a new connector in Elastic that points to the Jira Service Management / Operations API (or webhook) instead of the Opsgenie URL.  

- Update your rules to use that new connector and adjust any payload/field mapping as needed.

Atlassian treats this as a post‑migration task: Opsgenie APIs keep working during the move, but after the migration you’re expected to switch your external tools (like Elastic) over to the new JSM endpoints and eventually decommission the old Opsgenie connector.

Greetings, 

Alex

[Guneycan Sanli]

Thanks a lot Alex!