[HN Gopher] Atlassian announces end of support for Opsgenie
___________________________________________________________________
Atlassian announces end of support for Opsgenie
Author : anurag
Score : 80 points
Date : 2025-03-06 18:08 UTC (4 hours ago)
(HTM) web link (www.atlassian.com)
(TXT) w3m dump (www.atlassian.com)
| cj wrote:
| This appears to be more of a pricing/packaging/branding change as
| opposed to Atlassian shutting something down.
| bovermyer wrote:
| 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.
| hinkley wrote:
| Atlassian is nothing if not consistently mediocre at
| integrating their purchased properties into each other.
|
| And they still haven't finished making deployments have
| feature parity with builds in Bamboo.
|
| I made it partway through the interview process at a startup
| a couple weeks ago and realized I didn't have a good answer
| if they asked my advice for what to use for project
| management, if not Atlassian. Which was fairly likely given
| the company maturity and the position. I'm still trying to
| find that answer.
|
| Aside from GitHub I only have one other answer and it starts
| with, "this is going to sound crazy but hear me out."
| no_wizard wrote:
| There's Linear, there's GitHub / Gitlab issues and
| projects, there's Asana (has all the features, simply
| called different things in many cases)
|
| Once you start to see Jira as 'central repository for
| realizing work streams' the options become easier to
| assess.
|
| The place where Jira does sem to excel is automations, but
| I think thats simply due to maturity and alot of platforms
| cover most common ground
| datadrivenangel wrote:
| What's the answer? Excel?
| devmor wrote:
| I'm a fan of whiteboard and sticky notes!
|
| Distributed scaling is a little difficult, you have to
| set up a webcam and hire an intern to move things around,
| but it's probably still cheaper than a lot of enterprise
| solutions.
| CobaltFire wrote:
| I legitimately used this method (updated three times a
| day) via a photo posted to a spot on sharepoint in the
| military.
|
| People LOVED it. Worked amazingly well, was easy to hand
| off if I was out, etc.
| burningChrome wrote:
| >> Atlassian is nothing if not consistently mediocre at
| integrating their purchased properties into each other.
|
| I can't think of any company off the top of my head that
| has acquired a company and successfully integrated their
| tech stack into their own product offering. I work for a
| huge health care company whose stated goals are to grow
| through acquisition and in the 5 years I've been here, none
| of the painfully long process of integrating another
| companies tech has gone well - at all.
|
| If anybody has any good examples of this happening, I would
| love to read about them.
| tim-- wrote:
| Apple with TestFlight (Burstly) comes to mind.
| javawizard wrote:
| > Aside from GitHub I only have one other answer and it
| starts with, "this is going to sound crazy but hear me
| out."
|
| Do tell...
| hinkley wrote:
| Someone years ago "foisted" Trac on us. This is before
| CI/CD had reached the status of a default behavior.
|
| I thought it was going to be a shitshow but it turned out
| to hit the Pareto Front for project management,
| especially if you were doing Kanban. It's one of the
| first tools that auto-linked between wiki, tickets,
| commits and commit messages. You could put ticket numbers
| and Wikiwords into your commit messages and it just
| worked.
|
| I'm trying to design a Trac but with CI now, but I'm
| working on a personal time management app instead,
| because I don't build panipticons, so those features need
| to live where management cannot see.
| achow wrote:
| OpsGenie was acquired for $295M in 2019.
|
| https://webrazzi.com/en/2019/08/08/5-reasons-why-atlassian-b...
| eastbound wrote:
| 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.
| ethbr1 wrote:
| It's probably the Salesforce approach, which is letting product
| sellers drive architecture, which is always "This one customer
| needs this thing exactly like this" => now there's n+1 flavors
| of the product.
| ksmith14 wrote:
| 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.
| orphea wrote:
| Two alternatives Atlassian itself suggests have free tier:
|
| https://www.atlassian.com/software/jira/service-management/p...
|
| https://www.atlassian.com/software/compass/pricing
| evil-olive wrote:
| depending on what you're using it for, Pushover [0] might fit
| the bill. it's what I use for my home monitoring setup - low-
| priority alerts just go to an email folder, but a high-priority
| alert (such as a water leak sensor firing) will get pushed to
| my phone.
|
| it's a "no frills, in a good way" type of product. dirt-simple
| API with straightforward pricing ($5 lifetime subscription) and
| limits so generous I've never worried about hitting them (10k
| messages/month).
|
| 0: https://pushover.net/
| Attackerabu wrote:
| How about AlertOps? Is it a suitable alternative?
| hinkley wrote:
| 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.
| jjtang1 wrote:
| [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.
| hitekker wrote:
| Thank you for the clear disclaimer. It's an elegant way to
| conserve or draw attention in a forum.
|
| One small bit: maybe include a link to your website? That would
| make it easier to clickthrough and looksee
| jjtang1 wrote:
| I thought maybe a link was TOO promotional haha.
|
| https://rootly.com/ || and Opsgenie comparison (features):
| https://rootly.com/comparisons/opsgenie-vs-rootly-on-call
| bovermyer wrote:
| Well, I find myself looking at alternatives suddenly.
|
| However, one make-or-break feature - does Rootly have a
| Terraform provider? We rely heavily on Terraform for building
| out our Opsgenie setup.
| jorams wrote:
| Seems so, a quick search turned up this[1]
|
| [1]: https://registry.terraform.io/providers/rootlyhq/rootly/
| late...
| jjtang1 wrote:
| Ah yes. Terraform is super popular for us (almost 1m
| downloads). We also built a pretty cool "Terraformer" tool
| that lets you create workflows in UI and translate that to
| .tf easily.
|
| We take extensibility pretty seriously. Outside the basics,
| we just released our own agent ready API
| (https://rootly.com/blog/introducing-rootlys-api-ai-agent-
| fir...), MCP, docs are now LLM ready
| (https://docs.rootly.com/llms-full.txt).
| karamanolev wrote:
| We're a small team (15 engineers) running a popular local
| service in Eastern Europe. We'll be checking that out.
|
| I don't get the pricing of PagerDuty and OpsGenie. It seems too
| expensive for us. We're only a few people on-call and we need
| something simple, barebones, that just works and works
| reliably.
| jjtang1 wrote:
| 15 eng prob falls nicely into our startup offering, would be
| pretty discounted: https://rootly.com/startups
|
| You get on-call + incident response + status pages. And a
| pretty "defaults only" experience ootb.
| darkwater wrote:
| 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 understand, big
| enterprises as clients which are notoriously slow, being the
| incumbent and being a big corporation yourself, but still, I
| don't get it.
|
| [1] https://rootly.com/landing/pagerduty-vs-rootly-on-call
| jjtang1 wrote:
| Not trying to dunk on my competition but that is one thing
| that always surprised me too. Speed to deliver/innovate. I
| see large corporations all the time like even Slack (Agent
| marketplace), AWS (Bedrock), deliver at a high clip. PD truly
| had the opportunity to be a Datadog sized company given the
| brand name. Now it's a reputation impossible to shake.
|
| There are some pretty low hanging fruit stuff that would make
| the PD experience palatable (e.g. ability to page teams not
| just services, allow for partial overrides). These things for
| us were <1 week projects.
|
| I do think PD is trying to rectify it by acquiring Jeli,
| giving it away for free in their new pricing plan, etc. Def
| feeling the squeeze a bit if I had to guess.
| jurajmasar wrote:
| At the risk of being banned forever on HN:
|
| <self-promotion>
|
| We built Better Stack (https://betterstack.com/incident-
| management) 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>
| MarekDlugos wrote:
| This is cool. Happy Better Stack customer here.
| shric wrote:
| Perhaps I'm in the minority, but I was immediately put off when
| I saw "AI-native" on that page.
|
| I don't want my incident management system to be AI anything.
| But then I thought maybe I'm being unreasonable so I checked
| out https://betterstack.com/docs/uptime/incident-silencing/
| which was the first thing I found that was AI related.
|
| Frankly, the thought of some black box AI system deciding when
| to silence incidents utterly terrifies me. I want to be
| absolutely 100% certain that I'm receiving all my alerts. If
| they're too noisy or repetitive, it's on me and my team to
| improve the alert quality, not leave it to "AI" to figure out
| what to silence.
| jurajmasar wrote:
| Thanks for the feedback!
|
| The phrase "AI-native" increases your startup's valuation by
| 100x nowadays
|
| (just kidding)
| shric wrote:
| 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.
|
| https://github.com/opsgenie/opsgenie-go-sdk-v2/pull/89
| gregdoesit wrote:
| 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] https://newsletter.pragmaticengineer.com/i/52148641/what-
| atl...
| atonse wrote:
| Probably prioritizing their revenue generating products over
| ones that may have had very little revenue.
| caseyy wrote:
| It is evolving... backwards into non existence.
| rdsubhas wrote:
| 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.
| thesh4d0w wrote:
| > 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?
| rdsubhas wrote:
| Indeed, you are right. The title is clickbait. I'll edit.
| rat9988 wrote:
| I'm not sure it is. It looks pretty reasonable. I'm not
| sure about what your whole outrage is. You are a paying
| customer, so they have to send you an email before they do
| the public announcement?
| tgv wrote:
| Sounds reasonable. The public has little to no interest
| in opsgenie, but paying customers do.
| darkwater wrote:
| Yes, they should have done exactly that. Do you think
| it's ok how they managed it?
| x3n0ph3n3 wrote:
| My company literally _just left_ PagerDuty for OpsGenie. It's
| a pretty big gut punch after just doing all the work to cut
| over.
| MajimasEyepatch wrote:
| The title isn't misleading. Maybe it would be helpful if it
| included the date, but no company the size of Atlassian is
| going to shut down a product like Opsgenie without a window for
| people to migrate. This seems to be a fairly generous window.
| birol wrote:
| 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?
| haney wrote:
| 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.
| mads_quist wrote:
| 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:
| https://allquiet.app/opsgenie-alternative
| armiiller wrote:
| Founder of https://pagertree.com - If you are looking to switch
| from OpsGenie, make sure to check PagerTree out.
|
| Our teams feature is most like OpsGenie compared with others.
| piotrkulpinski wrote:
| 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.
| altairprime wrote:
| [delayed]
___________________________________________________________________
(page generated 2025-03-06 23:01 UTC)