Operations | Monitoring | ITSM | DevOps | Cloud

There is a paradox at the heart of serverless. While it’s promoted as a very agile way to develop, a way to push your product as fast as possible to your customers, many development teams find it really difficult to work fast. Why does this happen and can we solve the issue? Let’s start with what makes serverless such a powerful paradigm. Serverless rests on three legs, each of which contributes to the agility that serverless is known for.

I’ve said this before, but I’m saying it again: observability is not a synonym for monitoring, and there are no three pillars. The pillars are bullshit.

By Des Nnochiri Most enterprises now use two or more cloud service providers, and 35% use up to five monitoring tools to keep tabs on hybrid cloud and multi-cloud environments. Even before organizations began shifting software and IT infrastructure to the cloud, a typical business would use four to ten tools just to monitor and troubleshoot their internal networks, according to analyst and consulting firm Enterprise Management Associates.

Recently, we ran into a problem where a customer’s dashboard broke to such an extent that it hung on loading. This is a really rare problem and in this case was an instance where the customer had created a variable that referenced itself. Once the dashboard is broken in this way, it is impossible to reach a screen allowing you to remove that variable. This post is not about how it was broken, but about how we resolved the error.

We live in a digital world, and it’s becoming more and more apparent every day. We rely on our smartphones to give us directions to where we need to go. We rely on email to share information with our colleagues, family and friends. We access our medical records through online portals. We even hail a rideshare through an app that connects us to drivers in locations across the globe.