Atlassian announces end of support for Opsgenie

95 点作者 anurag2 个月前

25 条评论

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 you're flying in the dark. And yet, Atlassian did not prioritize restoring OpsGenie.I covered the details at the time [1]. To this date, this incident is a real head-scratcher and makes me wonder if Atlassian has internalized how much more critical an incident alerting software is, compared to a ticketing software (JIRA) or wiki (Confluent).[1] <a href="https://newsletter.pragmaticengineer.com/i/52148641/what-atlassian-customers-are-saying" rel="nofollow">https://newsletter.pragmaticengineer.com/i/52148641/what-atl...</a>

评论 #43284941 未加载

评论 #43286487 未加载

achow2 个月前

OpsGenie was acquired for $295M in 2019.<a href="https://webrazzi.com/en/2019/08/08/5-reasons-why-atlassian-bought-opsgenie-for-295m/" rel="nofollow">https://webrazzi.com/en/2019/08/08/5-reasons-why-atlassian-b...</a>

jjtang12 个月前

[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 is worth checking out (Slack-native, holiday scheduling, request coverage, clean mobile app, etc).Previous to Rootly I worked at Instacart where I helped us transition from PD to Opsgenie. Afterwards, still not being happy I built Rootly.Today, we've helped Trivago, Motive, Yahoo, and quite a few others make the switch. Pretty easy with our importer tool, etc.

评论 #43286152 未加载

评论 #43285620 未加载

评论 #43284433 未加载

评论 #43285105 未加载

评论 #43286786 未加载

评论 #43285027 未加载

rdsubhas2 个月前

EDIT:::: The title submitted (End of support) is a bit misleading. It's set to April 2027. I've left my original message here for brevity. Not all of it is valid, but some is.Super bizarre. We're a large Opsgenie customer. The Opsgenie website or mobile apps never showed any notice, not even as of now. The "Announcements" section in the mobile and web apps as I'm writing reads a feature announcement: "Coming soon: Simplified integration setup experience!"Our customer relationship nor billing teams never received any communication.Atlassian — we don't mind you sunsetting any product, that's fine. But honestly, your paying customers shouldn't get to know this from a blog post in social media, especially for an On-call emergency product.I wouldn't trust any product from Atlassian after this fiasco.

评论 #43284817 未加载

评论 #43285077 未加载

评论 #43289338 未加载

eastbound2 个月前

We aren’t subscribed to OpsGenie but Jira sends OpsGenie notifications all the time and it’s impossible to unsubscribe, because you need to cancel OpsGenie which we don’t have.Anyway the product map of Atlassian is unreadable now (Jira Work ≠ Jira Portfolio ≠ Jira Software ≠ Jira Service Management, all in Jira), and they don’t make clear what you’re subscribed to in the administration: Products, addons, same products but other sites, etc. This mess is downright visible in the announcement:> 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.I think they botched the project where they unified the login, and failed to make a centralized dashboard. In any case, I always wonder whether that’s intentional or a dedicated effort to make people spend more.

评论 #43283522 未加载

shric2 个月前

From my point of view they ended support a long time ago.Sep 8, 2022 - I sent a 2 line PR to fix an incorrect spelling of a json field and add a missing one in their Go SDK.June 23, 2023 (9 months later) - It was reviewed and merged.<a href="https://github.com/opsgenie/opsgenie-go-sdk-v2/pull/89">https://github.com/opsgenie/opsgenie-go-sdk-v2/pull/89</a>

评论 #43286189 未加载

jurajmasar2 个月前

At the risk of being banned forever on HN:<self-promotion>We built Better Stack (<a href="https://betterstack.com/incident-management" rel="nofollow">https://betterstack.com/incident-management</a>) after being frustrated with PagerDuty a couple years back. It's a solid place to land if you need to migrate away from Opsgenie.Let me know at juraj@betterstack.com if you have questions, happy to help! (I'm the founder)</self-promotion>

评论 #43286268 未加载

评论 #43285975 未加载

评论 #43285057 未加载

评论 #43284717 未加载

评论 #43284529 未加载

rohgpt2 个月前

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 - <a href="http://zenduty.com/zenduty-the-best-opsgenie-alternative-compare/" rel="nofollow">http://zenduty.com/zenduty-the-best-opsgenie-alternative-com...</a>

评论 #43289395 未加载

cj2 个月前

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

评论 #43283670 未加载

评论 #43289645 未加载

Aeolun2 个月前

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?

评论 #43287762 未加载

评论 #43286504 未加载

ksmith142 个月前

I’ve been using OpsGenie’s free tier for a number of years as part of a home automation/monitoring project. Guess it’s time to shop for alternatives.

评论 #43283610 未加载

评论 #43285314 未加载

评论 #43288070 未加载

haney2 个月前

It's wild to me that they would acquire a company for $295m and then shut it down six years later. I'd be really curious to know if this is a failed acquisition or if they think they'll be able to retain previous ops genie customers on their new products.

评论 #43286528 未加载

booster012 个月前

I was notified about OpsGenie's closure by a client who was simultaneously testing both OpsGenie and our system, TaskCall (<a href="https://taskcallapp.com" rel="nofollow">https://taskcallapp.com</a>) 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: <a href="https://medium.com/@riasat.ullah/opsgenie-reaches-end-of-life-38399b4e2564" rel="nofollow">https://medium.com/@riasat.ullah/opsgenie-reaches-end-of-lif...</a>

piotrkulpinski2 个月前

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

评论 #43292171 未加载

评论 #43291684 未加载

amalkiran2 个月前

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 <a href="https://www.temperstack.com" rel="nofollow">https://www.temperstack.com</a>. 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

jschumacher2 个月前

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.

altairprime2 个月前

I’ve never seen a press release behind a captcha before. It showed me nine buckets and asked me to select the buckets. If someone has a mirror?

hinkley2 个月前

One of the pointless games of musical chairs at my last job was migrating to OpsGenie.The amount of opportunity costs that racked up nearly killed them.

sirinett2 个月前

Hi all, here is a recent guide on Incident Management Buyer's Guide, I hope this helps while you look for an alternative: <a href="https://www.ilert.com/incident-management-buyers-guide/is-this-guide-for-you" rel="nofollow">https://www.ilert.com/incident-management-buyers-guide/is-th...</a>

smoyer2 个月前

"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.

评论 #43288077 未加载

armiiller2 个月前

Founder of <a href="https://pagertree.com" rel="nofollow">https://pagertree.com</a> - If you are looking to switch from OpsGenie, make sure to check PagerTree out.Our teams feature is most like OpsGenie compared with others.

mads_quist2 个月前

Founder of All Quiet here. Sorry - this is also promotional :)We've created All Quiet as an Alternative to Opsgenie and PagerDuty et al. We are building an incident management platform for developers from developers. We devs don't need a "full service platform" that also brews our team's coffee. We simply want to get a critical notification on our phones when sth's broken.Check out how we compare to Opsgenie: <a href="https://allquiet.app/opsgenie-alternative" rel="nofollow">https://allquiet.app/opsgenie-alternative</a>

评论 #43286250 未加载

caseyy2 个月前

It is evolving… backwards into non existence.

Attackerabu2 个月前

How about AlertOps? Is it a suitable alternative?

birol2 个月前

Founder of ilert.com here.For months, we’ve heard from customers jumping ship to ilert, citing Opsgenie’s stagnation as Atlassian folded its features into Jira Service Management (JSM). JSM’s a beefy ITSM platform - great if you need the extras, overkill if you just want real-time incident response.Now there’s Compass: a dev-centric service catalog with basic alerting, on-call, and real-time notifications. Replacement or sidekick? Compass is a standalone Opsgenie successor for devs, yet it complements JSM’s broader IT support scope. Together, they tag-team the incident game, but neither fully mirrors Opsgenie’s features.ilert’s the alternative: a German-built incident response tool covering alerting, on-call, status pages, and call routing—tightly focused.Thoughts? Any existing customers following one of the migration paths suggested by Atlassian?

评论 #43289341 未加载