One of the most impressive books on DevOps, “The DevOps Handbook”, emphasis three fundamental principles underpinning DevOps: systems thinking, amplify feedback loops, and continual experimentation & learning. Amplifying feedback loops is described as creating the right to left feedback loops, which helps corrections to be made continually, by Gene Kim in his blog post. But, let’s start with why we should do this in the first place.

Hi there! this is the first post on Statuspal’s young life :) we’ll be using this publication to communicate about new and upcoming features on our beloved platform and of course all things related to status pages & monitoring. First, an introduction is in order, Statuspal aims to solve a subtle but important problem, status communication & monitoring, sometimes sites go down, no matter how perfectly engineered they are, they will go down.

Imagine the following scenario: A critical incident hits. You have a few different teams on it throughout the company. Managers and other stakeholders need to be updated every thirty minutes. But the biggest issue is that you need to engage with external service providers. You need your communication provider and hosting service to check on their side and report back. You want a consultant in the picture and an external help desk service might be involved as well.

DevOps teams use a number of monitoring, project management, log management, and other IT management tools to receive alerts when something’s up. While this helps IT teams keep their system up and running at all times, the content of the alerts sent by some applications might not be relevant or insightful to the technicians who work on those issues. Now, with the Alarm Modifier feature, you can add new fields to an alarm, modify existing fields, rename fields, or remove them altogether.

Automatic Twitter posts from Statuspage incident updates now link together into one Twitter thread. This update applies to Tweets that are posted automatically via the Statuspage Twitter integration.