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.

Over the past decade, multiple scientific studies have confirmed what we in DevOps have known for ages: Being on-call is a pain! But just how bad is it?

Dashboards are great, but what if you're not checking them? Wouldn't it be great to know when you have a huge spike in traffic, or if you're about to hit your concurrent connections limit for a single database? Don't worry, Google Stackdriver Alerts have you covered!

Not all websites are the same. From personal blogs to business websites, online shops to community forums, SaaS applications to video streaming services, websites come in all shapes, sizes and flavours. It follows that not all websites have the same uptime requirements. If a personal blog goes down for 20 minutes it might not be a big problem, but the same downtime for a popular online shop could be a major concern.