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

Inside the longest Atlassian outage

newsletter.pragmaticengineer.com

Post reply on HN
Print view View original

581–590 of 772 posts

Re: Inside the longest Atlassian outage

#581

Post by zmmmmm »

tpmx wrote: post #464
Aissen wrote: post #322

Earlier quoted context omitted.

From the article: > Atlassian claims the customers impacted were “only” 0.18% of its customer base at 400 companies. From https://jira-software.status.atlassian.com/ : > The team is continuing the restoration process for the ~400 impacted customers.

> The team is continuing the restoration process for the ~400 impacted customers. We have restored functionality for 45% of impacted users. If this is truthful it implies implies more than 400 impacted customers.

even in the middle of the crisis they will play with ambiguity around the words "user" and "customer" to obfuscate the real situation (presumably they don't consider users 'customers', which goes right to the heart of enterprise software in general)

Re: Inside the longest Atlassian outage

#582

Post by takeitaussie »

mdoms wrote: post #572
kingofpandora wrote: post #458

Engineering mistakes happen. The most inexcusable thing is not communicating with the paying customers who have been affected for over a week. Atlassian's Global Head of Customer Success probably should have been fired but here she is promoting Atlassian Cloud on LinkedIn three days ago: https://www.linkedin.com/mwlite/in/gertie-rizzo-5b70061 Actually reading a bit more, it seems like their customer team was partying…

A lot of people talking about "firing" in this thread. That's not how Atlassian operates, to their credit. It probably comes from their Australian DNA.

True. Like their laid back approach to operations.

Re: Inside the longest Atlassian outage

#583

Post by zmmmmm »

jmondi wrote: post #110

What blow's my mind is that Atlassian stock has barely taken a hit...

in some ways it should be bolstered by this because most of the customers appear helpless, just passively waiting for their data to be restored. It shows that Atlassian have them at their mercy and it must therefore suggest that there is a lot of lattitude to extort more out of them through abusive licensing terms / price increases in the future.

Re: Inside the longest Atlassian outage

#585

Post by _moof »

kingofpandora wrote: post #458

Engineering mistakes happen. The most inexcusable thing is not communicating with the paying customers who have been affected for over a week. Atlassian's Global Head of Customer Success probably should have been fired but here she is promoting Atlassian Cloud on LinkedIn three days ago: https://www.linkedin.com/mwlite/in/gertie-rizzo-5b70061 Actually reading a bit more, it seems like their customer team was partying…

These are base instincts speaking. Emotional, vengeful, a desire to punish because you've been hurt. It's perfectly natural to feel that way, but it's not reasonable, fair, or effective.

Re: Inside the longest Atlassian outage

#587

Post by takeitaussie »

NationalPark wrote: post #312
kgeist wrote: post #142

We use on-premises setups for almost everything (we generally avoid cloud solutions to have full control of our data), sometimes (approximately once a month) it goes down for a few minutes which already feels like a torture because all our processes depend on it, I can't imagine having no access to it for several weeks, all our work would stop to a halt... The office of the guy who administers on-premise servers is l…

What do you do if the on-premises guy gets hit by a car and isn't in his office?

What do you do if your cloud provider is down for 3 weeks?

Re: Inside the longest Atlassian outage

#588

Post by TrevorAustin »

passerby1 wrote: post #586

Do anyone seriously consider changing Jira/confluence to some alternative after this? I personally stopped using Jira a couple of years ago in projects I lead.

Some PMs at my company have been agitating for a switch from Asana to Jira, and now I (as VP Engineering) can guarantee that will never, ever happen.

Re: Inside the longest Atlassian outage

#589

Post by lttlrck »

notdang wrote: post #70
mkl95 wrote: post #23

Earlier quoted context omitted.

> Communication gap. First, there was a communication gap between the team that requested the deactivation and the team that ran the deactivation. Instead of providing the IDs of the intended app being marked for deactivation, the team provided the IDs of the entire cloud site where the apps were to be deactivated. So what they are saying is that they are not testing scripts at some staging server before running them…

it seems that it worked as intended, thus they have a QA process. The problem was in the wrong IDs provided and I doubt that at their scale they have a staging environment that duplicates the customer data.

--dry-run and verify the output

Re: Inside the longest Atlassian outage

#590

Post by magicalhippo »

Phelinofist wrote: post #356
ordiel wrote: post #266

All I can say as an Attlassian Server products user is that the moment they say it was Cloud or nothing, I choose nothing. I much rather running Gittea on a raspberry pi that I CONTROL than having to have the impotence of doing nothing for more than a week. + having work at cloud companies and having been requested to "collect customer data" to hand it over to the government I would NEVER move critical pieces to anyo…

As I understood it is not "Cloud or Nothing" but "Cloud or Data Center" - is this wrong?

We're a team with effectively is Cloud or nothing, and we weren't very keen on going Cloud even before this current clusterf...
Post reply on HN