Opsgenie to JSM migration

I got this question from a customer:

“CMK has a built-in opsgenie plugin that will most likely need updating. Opsgenie was purchased by Jira and is being integrated into JSM. It appears that at some indeterminate time, the opsgenie API will go away.”

I suspect that in the future, an update will be released by the CheckMK developers to handle this acquisition and merger.

I have not found anything here or otherwise on the web to answer this. Anyone know?

2 Likes

Sorry for the ping, but @Sara might you know or know who can answer?

No problem Brian, I already got into some research on this after you initially posted.

I asked the person working on the component about this after doing a little internal research but currently I do not have any updates.
If it is possible, could you please create a support ticket?

Is there any update on this?

Nothing yet, unfortunately.

As soon as I got any news, I will update the thread :+1:

Hi @briand, hi @jestertoo

We plan to investigate Jira Service Management and Compass integrations with Checkmk, but there is no definite timeline yet, in part due to very little information from Atlassian/Jira. We are in contact with some Atlassian partners and hope to have more insights soon!
As soon as we have something more concrete, I will update this thread!

Cheers
Tanja

2 Likes

sorry to ping here again - should we use the opsgenie plugin or jira JSM?

The Opsgenie plugin works fine against JSM after the migration. Just make sure that the integration is setup correctly in JSM Operations using the API integration method.

One thing I noticed is that I had to re-apply the API key to the Opsgenie notification method after upgrading to 2.4. Apart from that all working as expected.

2 Likes

Opsgenie DOES continue to work fine after the migration.

I was asking for CMK to work with Atlassian to make sure it’s not going to break at some point in the future… IE api endpoint goes away, changes name, etc.

Thanks for the tip about updating to 2.4

Hi @jestertoo

Thanks for the follow-up! While I don’t have a concrete update yet (we’re still investigating), by now, we think that the Jira integration should also work with JSM, as they share a similar API. We have not yet tested that, so I can’t say for sure.

Also, a heads-up: Opsgenie support will officially end on April 5th, 2027. After that date, Opsgenie will no longer be accessible, and the Checkmk integration will obviously stop working.

As soon as I have any concrete information about the compatibility of JSM and our plans for Compass, I will update this thread.

Cheers
Tanja

2 Likes

@theyken Thank you for the response.

To confuse things, there are two different opsgenie/JSM integration/notification methods.

  1. built into CMK (the one I’m using as it has functionality to pass info on to JSM)

  2. opsgenie/JSM 3rd party script provided here:
    https://raw.githubusercontent.com/opsgenie/opsgenie-integration/master/check_mk/opsgenie

Good point! When I talk about notification integration, I’m always referring to the built-in ones unless I state otherwise :slight_smile:

What is the correct method in CheckMK to send pages via Jira oncall (part of Jira service management) now? I have yet to find a definitive answer.

  1. Configure the notification method on CMK with the Opsgenie plugin.
  2. Configure an API Integration in JSM Operations (the API key provided at this step needs to be taken and configured into the notification setup above).
  3. Configure the alert processing rules in JSM Operations.

Step 3 gives you the “glue” to take the CMK alert and do something with it inside JSM.

Once setup you can have your alerts going through and being notified based on your on-call schedule. You also have the option to create a incident in JSM that allows for assignment and tracking of the incident inside JSM.

It works well. I’m not sure if there is a more recent integration for this but we have this running across multiple sites and customers and its been reliable for years.