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.

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.

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.

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