Live data from Hacker News

Atlassian announces end of support for Opsgenie

atlassian.com

101–108 of 108 posts

Re: Atlassian announces end of support for Opsgenie

#101
I was at Atlassian during the OpsGenie acquisition and part of that process. Honestly, the biggest surprise to me was how long it took to shut down OpsGenie as a standalone product.

The broader trend here is the shift from unbundling to consolidation. Over the past decade, many “features” were created as standalone SaaS products, but that era is winding down. We’re now seeing the pendulum swing back, with more consolidation across the industry.

In my opinion, OpsGenie should have been a built-in feature of Jira Service Management from day one of the acquisition.

Re: Atlassian announces end of support for Opsgenie

#102
This seems like the end of an era. While Pagerduty was always the most expensive, OpeGenie seemed like a good alternative for smaller teams.

But today's incident management needs to be a lot more than just paging.

For anyone looking to unlock a lot more value out of their incident management tool, may I suggest https://www.temperstack.com. A number of OpsGenie customers have already switched to Temperstack even before this announcement came out.

I'm one of the cofounders of Temperstack and have personally helped companies make this transition. And I would be happy to get you set up as well. Feel free to drop me a line on amal@temperstack.com

Re: Atlassian announces end of support for Opsgenie

#103
post #98

Here's a list of open source alternatives to switch to: https://openalternative.co/alternatives/opsgenie Most of them can be self-hosted so you won't be locked in in case that happens again.

Who alerts you when your own alerting system is down?

You set up another alerting system to watch the alerting system. Duh!

Re: Atlassian announces end of support for Opsgenie

#105
post #96
post #72

Earlier quoted context omitted.

Oof. On it!

You profile is pretty interesting. Lmk if you want to come on the pod!

Ha, fancy running into you two here.

+1 to checking out rootly, they have the friendliest people in the incident business

Re: Atlassian announces end of support for Opsgenie

#106
post #96

Earlier quoted context omitted.

You profile is pretty interesting. Lmk if you want to come on the pod!

Ha, fancy running into you two here. +1 to checking out rootly, they have the friendliest people in the incident business

You’re too kind :)

Re: Atlassian announces end of support for Opsgenie

#107
I was notified about OpsGenie's closure by a client who was simultaneously testing both OpsGenie and our system, TaskCall (https://taskcallapp.com) for their incident response and management and live call routing. It came across as a surprise although recently we had more of their clients moving over to TaskCall.

However, it was not easy to find the announcement about the closure. The title of the announcement was very confusing. That is why my teammate decided to write an article with a clearer title. He did highlight why moving to TaskCall would be easy for current OpsGenie clients without impacting their operations, but here is a link of to the article if anyone is interested: https://medium.com/@riasat.ullah/opsgenie-reaches-end-of-lif...

Re: Atlassian announces end of support for Opsgenie

#108
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…

Reading the comparison with PD [1] and having been a Pagerduty customer...even if it's promo material for a competitor, it resonates a LOT with my experience with PD (and boy, I do have experience with it). The web UI and the limitations around overrides, paging groups, escalation policies etc are all real and makes me wonder: how is it possible that a behemoth in the space like PD is stagnating like that? I understa…

PM from PD, chiming in here. tl;dr: we hear you and understand some of the challenges raised by that comparison sheet and frankly, we appreciate that folks like Rootly have challenged us to innovate in our core product more. And yeah, we're also pretty psyched to have the Jeli crew onboard, we think they're pretty smart, too. : ) As JJ calls out below, we've revamped our pricing plans to bring more incident management to all of our plans and spent a lot of time rethinking our chat experiences! (Again kudos to the Jeli crew!)

To not give too much of our roadmap away in a public forum, some of the basic components of overrides, paging groups and the web UI - keep your eyes peeled this year, one of our big focus areas is looking at how not only do we eliminate some of these gaps around on-call management and UI, but also going beyond just filling these table stakes. As you might imagine, PagerDuty scaled pretty aggressively (while also keeping our high reliability standards in place - customer trust is our #1 priority, after all we need to be up when everyone else is down), and we've had to make some investments to unlock our roadmap for this upcoming year.

Real talk though, happy to continue the conversation/ meet up over a zoom. Send me an email: dgodbout[@]pagerduty.com. There are humans over here at PagerDuty who care a lot about folks like yourself and I consider myself lucky to get build products for people who are responsible for ensuring things just "work".

Post reply on HN