OpsGenie end of life?

[Andrew Laden]

I just saw the email/notice about OpsGenie going end of life.

I don't see how Atlassian can claim that JSM or Compass can do anywhere near what OpsGenie can do in terms of Alert Management? Am I missing something?

I guess its back to PagerDuty? Something else? WHy are they killing a best of breed product in alert management.

[__ Jimi Wikman]

@Andrew Ladenyou have almost all functionality from Opsgenie in JSM today and a few extra things like automation. You might not have activated it yet as it is on a separate section, much like Assets are.

So you don't have to worry about losing the functionality of Opsgenie, but you will see it improved even as it is now tied into the incident workflow between JSM and Jira.

I wrote about this a long time ago here if you want more details:
https://www.linkedin.com/pulse/new-jira-incident-workflow-how-improve-we-work-today-jimi-wikman-viu3f/?trackingId=sWFKjef%2BStS5Ezk9D%2F5TSw%3D%3D

[Andrew Laden]

To be fair, I am an old school on prem Jira/confluence user, so I have not been keeping up with the featureset in JSM cloud.

I make heavy use of Integrations for alert processing. Deduplication, filtering, severity, routing, etc. ingestion via email, API, product integrations, alert enrichment etc. the alert ingestion and processing features are why I picked it over other competitors many years ago.  Basically I feed all alerts into opsgenie. and use the engine in there to determine if the alert is actionable, and if so, then create a jira ticket where the work is tracked. 

Does JSM cloud have any of that functionality? 

The on-call rotation, notification/escalation and incident management is secondary for me. 

[Mathew Lederman]

I've never used Opsgenie, so I can't speak to your specific question, but just wanted to offer a friendly word of caution: If you're used to Datacenter/Server JSM, be prepared for a rude awakening. JSM Cloud is 2-3 years behind it's Datacenter counterpart.