alertmanager icon indicating copy to clipboard operation
alertmanager copied to clipboard

Published 20 hours ago • verified publisher icon prometheus

jsm-prometheus integration

Open ozlemmcokuk opened this issue 1 year ago • 10 comments

ozlemmcokuk avatar Sep 11 '23 21:09 ozlemmcokuk

@zekihan @ozlemmcokuk is the JSM API compatible with OpsGenie?

jkroepke avatar Nov 09 '23 09:11 jkroepke

Hi @jkroepke Actually the endpoints for Opsgenie and Jira Service Management are not the same. We are bringing alert&on-call capabilities to Jira Service Management natively, so we will have a new integration on Jira Service Management product which will use this plugin as in Opsgenie. The functionality can be seen the same at first but the capabilities of Jira Service Management is much wider than Opsgenie as a product, so having a dedicated plugin will serve for visibility for both products.

ozlemmcokuk avatar Nov 21 '23 19:11 ozlemmcokuk

Hi @jkroepke Is there anything that we need to do in this PR?

ozlemmcokuk avatar Dec 01 '23 08:12 ozlemmcokuk

I don't know. I not a maintainer, I just had a questions, since we also having Jira and OpsGenie and we may play to merge them.

jkroepke avatar Dec 01 '23 08:12 jkroepke

Hi @simonpasquier, @w0rm and @gotjosh Could you please help us with our new integration? We are planning to release it in December. Please let us know if you have any comments about the PR. Thanks 🙏

ozlemmcokuk avatar Dec 03 '23 14:12 ozlemmcokuk

Whats happens, if you enter the JSM endpoints on the OpsGenie integration?

jkroepke avatar Dec 06 '23 08:12 jkroepke

@ozlemmcokuk

We ask the Jira support and they confirm that the API is equal to OpsGenie

Hello,

I am glad that the Incoming call integration is working as expected :slight_smile: Regarding the Prometheus and Heartbeats, I would like to inform you that there are no changes to the API keys these integration will continue working as it is.

As a side note, I would like to inform you that the Incoming call routing and Heartbeat feature is available only with the Jira Service Management Premium plan.

I hope I was able to answer your queries, in case you need further assistance on this ticket, please revert would be happy to help!!

Best Regards, Arjun Ganapathy Atlassian Cloud Support

Efficiently, the existing OpsGenie Integration could be used for JSM which make the PR pointless for me. Maintain duplicate code make no sense.

jkroepke avatar Dec 07 '23 07:12 jkroepke

Indeed if OpsGenie and JSM are just 2 sides of the same coin, I wouldn't create/maintain another integration.

simonpasquier avatar Dec 08 '23 15:12 simonpasquier

Even though the JSM and OpsGenie integrations are currently the same, Atlassian has stated their intention that the JSM features are going to diverge from OpsGenie in the future, and they are encouraging customers to switch over to the JSM Ops API.

https://support.atlassian.com/jira-service-management-cloud/docs/start-shifting-from-opsgenie-to-jira-service-management/

So even if there is not currently a need for a separate JSM receiver in prometheus, there probably will be a need for it in the semi-near future.

james00002 avatar Jul 17 '24 13:07 james00002

So even if there is not currently a need for a separate JSM receiver in prometheus

At the moment, die OpsGenie can be used with JSM endpoints, too

jkroepke avatar Jul 17 '24 14:07 jkroepke