Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atlassian announces end of support for Opsgenie

atlassian.com

Post reply on HN
Print view View original

71–80 of 108 posts

Re: Atlassian announces end of support for Opsgenie

#71

Post by jedberg »

jjtang1 wrote: post #13

[Promotional warning] Damn. As a founder in the incident management space (Rootly) I've had a lot of respect for Opsgenie. They had unique features like heartbeats and ran a lean but mighty team before selling to Atlassian. We saw them the most in Europe by far. Okay here comes to promotional part (don't hate me). If anyone is looking for a modern alternative to Opsgenie that isn't as expensive as PagerDuty, Rootly i…

Hey there, this page: https://rootly.com/humans-of-reliability

Is weirdly broken (at least for me) on Safari on desktop. Every mouse movement or key click causes all the tiles to enlarge.

It's fine on Chrome and Firefox.

Re: Atlassian announces end of support for Opsgenie

#72

Post by jjtang1 »

jedberg wrote: post #71
jjtang1 wrote: post #13

[Promotional warning] Damn. As a founder in the incident management space (Rootly) I've had a lot of respect for Opsgenie. They had unique features like heartbeats and ran a lean but mighty team before selling to Atlassian. We saw them the most in Europe by far. Okay here comes to promotional part (don't hate me). If anyone is looking for a modern alternative to Opsgenie that isn't as expensive as PagerDuty, Rootly i…

Hey there, this page: https://rootly.com/humans-of-reliability Is weirdly broken (at least for me) on Safari on desktop. Every mouse movement or key click causes all the tiles to enlarge. It's fine on Chrome and Firefox.

Oof. On it!

Re: Atlassian announces end of support for Opsgenie

#73

Post by smoyer »

"Starting today, there are two options for Opsgenie customers: move to Jira Service Management for robust end-to-end incident management, or move to Compass for alerting and on-call management alongside an intuitive software component catalog."

Or do something sane like move off Atlassian products completely.

Re: Atlassian announces end of support for Opsgenie

#74

Post by vasco »

atonse wrote: post #33
gregdoesit wrote: post #23

The most bizarre OpsGenie story was how in 2022, this tool was down for 2 weeks for hundreds of unlucky companies that were Atlassian customers. This was at a time when JIRA had an outage impacting a small percentage of their customer base - but still in the hundreds of organizations (with around tens of thousands of users.) While most companies can operate for some time without JIRA: losing your paging service means…

Probably prioritizing their revenue generating products over ones that may have had very little revenue.

Problem is that they instantly turned the less revenue product into something that was worth 0.

Re: Atlassian announces end of support for Opsgenie

#75

Post by lawrjone »

x3n0ph3n3 wrote: post #52
thesh4d0w wrote: post #27

Earlier quoted context omitted.

> We will be reaching out via email to provide a tailored recommendation for each Opsgenie site, highlighting the best fit for your team. > Opsgenie end of support – effective April 5th, 2027: A public post followed up by them reaching out individually (which takes time) along with a 2 year grace period, seems pretty reasonable?

My company literally _just left_ PagerDuty for OpsGenie. It's a pretty big gut punch after just doing all the work to cut over.

This really sucks, that is rough. When you’re buying from a company like Atlassian you don’t expect this to happen really.

The writing has been on the wall for a while with Opsgenie though. I work at incident.io and loads of our customers have had deprecation/migration warnings for a year or so now, pushing them away from Opsgenie and into different Atlassian products (with no migration plan, sadly).

It’s been great for us as they tend to move to us (we have good migration support for Opsgenie) but confusing to watch from the outside as Atlassian never stopped selling the product even while actively shutting accounts down.

Re: Atlassian announces end of support for Opsgenie

#76

Post by tsoldrin »

x3n0ph3n3 wrote: post #52
thesh4d0w wrote: post #27

Earlier quoted context omitted.

> We will be reaching out via email to provide a tailored recommendation for each Opsgenie site, highlighting the best fit for your team. > Opsgenie end of support – effective April 5th, 2027: A public post followed up by them reaching out individually (which takes time) along with a 2 year grace period, seems pretty reasonable?

My company literally _just left_ PagerDuty for OpsGenie. It's a pretty big gut punch after just doing all the work to cut over.

Except that nothing is going away. We did the same, migrate from PD to OpsGenie. As soon as they offered to use JSM instead, we tried it and it’s great. Only one mobile client for everything, all old OpsGenie integrations just keep running, you still have heartbeats. JSM is the same product, just integrated into Jira. If you have OpsGenie running, migrating to JSM is just the push of a button.

Re: Atlassian announces end of support for Opsgenie

#77

Post by lawrjone »

bovermyer wrote: post #8
cj wrote: post #2

This appears to be more of a pricing/packaging/branding change as opposed to Atlassian shutting something down.

As a current Opsgenie user, I disagree. They're splitting their incident management and alerting/on-call into two services - Jira Service Management and Compass, respectively. Both are terrible, and not at all one-to-one replacements.

I work at incident.io and we’ve had to help a number of our customers who were affected by this. While Atlassian frame it like you can migrate, there’s no official migration story and the feature lists don’t match at all.

We’ve got a good migration story (import OG schedules and escalation paths, etc) so most customers just migrate to us, but if you didn’t have that option the Atlassian migration is much more painful.

Re: Atlassian announces end of support for Opsgenie

#78

Post by lawrjone »

Aeolun wrote: post #59

This thread has four different promotions for alternative services I’ve seen. Is this an Atlassian thing? Where everyone dislikes their stiluff so much they want to build their own? Or is it like time-tracking, which is something everyone has built at least once in their career as a programmer?

It’s an alerting/incident response incumbents thing. Ask anyone how much PagerDuty/Opsgenie have improved in the last decade and you’ll have the answer!

There’s a first wave of incident startups that responded to the market having stagnated about 4 years ago (incident.io, FireHydrant, Rootly) then a slew of extremely recent (It’s weird that Opsgenie is just quitting that race but realistically they weren’t really competing in terms of pace of development. Felt more like Opsgenie was bought under the assumption IR was a ‘solved’ problem that Atlassian could just add to their stack and be done with it, while today it’s increasingly apparently that just paging someone is the smallest part.

Re: Atlassian announces end of support for Opsgenie

#80

Post by rohgpt »

This Opsgenie announcement has certainly sparked some interesting discussions. Reading through the HN thread, it's fascinating to see how many teams are in similar situations - either just migrated to Opsgenie (ouch!) or trying to figure out what their next move should be.

The confusion around what's actually happening is understandable. While services will continue until 2027, end-of-sale in 2025 means many teams are already evaluating alternatives rather than waiting for the last minute.

Something that really resonated with me from gregdoesit's comment was that reminder of the 2022 outage where OpsGenie was down for two weeks for some customers. That incident highlighted something we think about constantly at Zenduty: paging services are mission-critical infrastructure.

When your alerting system goes down, you're essentially flying blind. I've been working with teams dealing with exactly these transitions, and the migration challenges are real - it's never just "update a webhook URL" as someone mentioned. Your alert routing rules, escalation policies, on-call schedules, and integrations are complex systems that need careful migration.

What I'm curious about: for those of you considering alternatives, what features matter most to you? Is it reliability? Pricing? Integration flexibility? The ability to reduce alert fatigue? Feel free to drop your thoughts here or DM me. Always happy to chat about these challenges even if you're not looking at Zenduty specifically. These transitions are stressful, and having been through them myself, I know how disruptive they can be to engineering teams who just want to focus on building their products.

Here's a detailed comparison of all the opsgenie features and what you need to know before you decide to migrate to a different tool - http://zenduty.com/zenduty-the-best-opsgenie-alternative-com...

Post reply on HN