If your site's back end is down, the site itself should be saying something intelligent. ("Ngnix timeout", or Cloudflare's error message blaming the site server, is kind of lame, but it's something.)
Atlassian Acquires StatusPage
61–70 of 132 posts
Re: Atlassian Acquires StatusPage
#62As a happy StatusPage user, I am worried about this acquisition. Been more and more frustrated with Atlassian and recently we had to move away from HipChat due to multiple issues (constant downtimes). What are the good alternatives to StatusPage?
We use Cachet[1], an open source alternative. We checked out many status page services out there, but found it hard to understand how some of them (web apps with a handful of pages) were more expensive than our accounting system or project management services we subscribe to?!? [1] - https://cachethq.io/
I'm skeptical that running Cachet on your own servers would be cheaper than StatusPage's smallest plan, especially if you have any kind of redundancy in place.
Re: Atlassian Acquires StatusPage
#63I remember when I was doing a talk in Melbourne, another developer told me what he didn't like about Atlassian was that they essentially only had one product (was it Jira? or Confluence? can't remember) and almost everything else in their offering set; they bought from other people and re-engineered to fit into their product line. Having administered, Jira, Confluence and Bamboo servers (all with slightly different i…
Their biggest product is JIRA followed by Confluence. Let's look at acquisitions vs internal developments: - 2003: JIRA - In-house - ~2004: Confluence - In-house - ~2007: Fisheye, Crucible (code analysis) - Acquisition - ~2008: Bamboo (builds) - Acquisition - 2010: Bitbucket - Acquisition - 2011: SourceTree - Acquisition - ~2012: Bonfire (JIRA Capture - screencast bugcatcher) - In-house - ~2013: HipChat - Acquisition…
It depends on the brand.
Software is expected to be improved over time. Which implies a less-improved state as a starting point.
The idea that customers expect you to teleport to the Platonic ideal of a product isn't very realistic.
Re: Atlassian Acquires StatusPage
#64I usually use " http://www.downforeveryoneorjustme.com/" . If your site's back end is down, the site itself should be saying something intelligent. ("Ngnix timeout", or Cloudflare's error message blaming the site server, is kind of lame, but it's something.)
If you pay them.
Re: Atlassian Acquires StatusPage
#65I usually use " http://www.downforeveryoneorjustme.com/" . If your site's back end is down, the site itself should be saying something intelligent. ("Ngnix timeout", or Cloudflare's error message blaming the site server, is kind of lame, but it's something.)
Re: Atlassian Acquires StatusPage
#66I usually use " http://www.downforeveryoneorjustme.com/" . If your site's back end is down, the site itself should be saying something intelligent. ("Ngnix timeout", or Cloudflare's error message blaming the site server, is kind of lame, but it's something.)
Re: Atlassian Acquires StatusPage
#67This acquisition doesn't fill me with confidence for the future. StatusPage was a clean, simple, and intuitive service. Atlasssian's software is the opposite of clean, simple, and intuitive.
Re: Atlassian Acquires StatusPage
#68Earlier quoted context omitted.
We use Cachet[1], an open source alternative. We checked out many status page services out there, but found it hard to understand how some of them (web apps with a handful of pages) were more expensive than our accounting system or project management services we subscribe to?!? [1] - https://cachethq.io/
Status pages are best hosted offsite, which means status page companies can easily justify higher prices since the alternative is to run your own servers exclusively for the status page (can't just throw the status page software on your app server). I'm skeptical that running Cachet on your own servers would be cheaper than StatusPage's smallest plan, especially if you have any kind of redundancy in place.
That is enough redundancy for our little bootstrapped web app until we are large enough to be able to afford something better.
Re: Atlassian Acquires StatusPage
#69This acquisition doesn't fill me with confidence for the future. StatusPage was a clean, simple, and intuitive service. Atlasssian's software is the opposite of clean, simple, and intuitive.
Standalone product. I think it will be safe.
Re: Atlassian Acquires StatusPage
#70This acquisition doesn't fill me with confidence for the future. StatusPage was a clean, simple, and intuitive service. Atlasssian's software is the opposite of clean, simple, and intuitive.
Having used many different bug tracking, help desk, and ticketing softwares… Atlassian does a dam good job. Totally customizable screens, fields, and workflows with a modern UI. A decent webservice API I’ve integrated a few external tools into without much difficulty. I’ve also written a few gadgets and plugins and received a decent amount of attention through their plugin marketplace. Maybe the admin that setup your…
I think this is key. There's so much customization allowed that its easy to get wrong. Your experiences can vary drastically between a well configured instance and a poorly configured one.