This is a minor release to change some of the wordings in PushMon notifications.

With WordPress powering over 30% of the internet and a plugin ecosystem that allows anyone to write software which will execute code on your server, it’s no wonder that it’s become a popular target for hackers. As part of our Vulnerability Scanning service – which already checks for thousands of known software and configuration vulnerabilities for all major software products and operating systems – we now also test over 10,000 known WordPress vulnerabilities.

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.

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.

Since launching Stride into early access last September, we’ve been thrilled by the excitement we’ve seen from the tens of thousands of teams who have adopted it as their communication platform.Now, six months in, we’re sharing an update on how organizations around the world are using Stride to move their work forward.

This is the second part of our two-part article series devoted to Elasticsearch monitoring. The heading of this article refers to Dante Alighieri’s “Inferno”, in which Dante offers a tour through the nine increasingly terrifying levels of hell. Our journey into Elasticsearch monitoring was also filled with hardships, but we have overcome them and found solutions for each case.

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?

New quarter, major changes! Content Checker goes live, Application monitoring and more.

Each company wants to build the next unicorn. The next Facebook, the next Twitter, the next Quora. But this is rarely what they accomplish. I’ve seen it time and time again.

I've told about why we started to explore serverless in my previous post. And this one will be about what we did and how it went so far. We used to have 9 servers (i.e., AWS EC2 instances) on multiple availability zones, each running a docker engine and all were interconnected with Rancher.