Over the years here at Statuspage we’ve probably heard every version of the open source vs. paid status page argument. While we’re obviously fans of the SaaS model, we also know there are a lot of advantages to an open source status page for a lot of teams. We’ve even recommended that route to some potential customers we thought would have a better experience hosting their own open source page.
This morning, though, all of our backlogs were a little harder to sift through thanks to a Slack outage in Europe and the US. To calm down, some of us might have turned to our Google Home or Chromecast to unwind while the outage hours piled up, only to find those were down too! What a morning!Now that Slack is running again, let’s take a moment to reflect on what the outage means and what we can learn from it.
Today we are happy to announce the general availability of CFEngine 3.12.0 LTS! This release has a lot of new features, and we are very excited about all the new possibilities you get with CFEngine 3.12.0 LTS. If you are using the previous LTS, 3.10 you will also benefit from all the new features, improvements and testing of the 3.11 release, which you can read more about in the CFEngine 3.11 release post.
Some companies, such as ecommerce businesses, are built from the ground up on the cloud, while others have a more traditional operating model, but all can benefit from using the cloud in their operations. Some of the primary reasons include: Achieve Business Growth, Increase Efficiency & Improve Customer and User Experience.
Ziv Levy, Software Engineer at Wix (a Sentry customer), recently faced two challenges: simulating a bug in Wix code and testing report data. His recent blog post, Meet Raven TestKit: Wix Engineering’s Open Source Tool to Test Sentry Reports, dices into how a plugin for Sentry’s Raven SDK helped him tackle those challenges, with specific documentation detailing what made the choice so simple. Read the post below, and then go try Raven TestKit for yourself (please, and thank you).
At Mattermost, we set out to build a platform that supports the world’s largest enterprises. To do that, Mattermost needs to be able to accommodate tens of thousands of simultaneous users, all of whom are using the platform in various ways at the same time.
Supporting a growing software team is a daunting challenge, and Git is often at the heart of that task. Ensuring developers can effectively collaborate requires user provisioning, tool permissions, and enough horsepower to support all of the load. If you support a distributed team, the factors become more complex. How do you ensure developers have a consistent experience across geographies and help productivity flourish?
The recent 5.1 release focused on smoothing out the rough edges from the 5.0 release. The major highlights of the Grafana 5.2 release are these two much-requested, long-awaited features.
An incident postmortem is an excellent framework for learning from incidents and turning problems into progress. It also builds trust with customers, colleagues, and end users (basically the folks affected by the incident) and lets them know your team is working to minimize future incidents and impact.
