Whether you are new to the Cloud, mid-transition, or a professional at cloud or hybrid systems, no one likes being bothered with useless alerts. The options are simple: If you take the approach of ignoring the alert like a bad cold-call, you risk the chance of missing a critical alert and watching your system crash around you. No one likes to open their inbox to a few hundred alerts they have been ignoring.

I have worked at Virtana for nearly 9 years. During that time, I have had the pleasure to interact with customers, prospects, and partners around the world. The types of conversations I have participated in have dramatically shifted during that time. Back in September 2011, the dialogues were largely focused on Storage Area Network (SAN) infrastructure, and how Virtana could provide performance assurances targeted at this environment. Over time, the conversations have broadened dramatically.

In the second episode of the Shifting Left podcast, we sat down with one of our resident cloud experts, Vikram Parmar, to get his take on how IT leaders can avoid the often-times spiraling cost of cloud investment.

In previous and great articles in here, we already talked about what Cloud is and the types that exist floating above our heads. But today, for a change, we want to focus more on one of its totally forgotten key aspects: Are clouds actually made of childish dreams and cotton candy? No! Just kidding! Today we are going to talk in “Pandora FMS discussions” about what cloud service types there are.

The modern enterprise has expanded its reach by using the power of cloud computing. However, with that power comes complexity in leveraging the multiple platforms needed to provide rich functionality. To achieve a seamless integration that involves multiple cloud infrastructures you need insightful and actionable data. You also need the right team to bring the clouds together in a seamless, effective, and efficient manner.

As organizations build out their serverless footprint, they might find themselves managing hundreds or thousands of individual components (e.g., Amazon S3 buckets, Amazon DynamoDB tables, AWS SQS queues) for just a single application. At the same time, performance issues can crop up at any of these points, which means that having access to detailed observability data from your serverless functions is crucial for effective troubleshooting.

To me personally, when I think programming languages I think JavaScript and while 67% of the developers out there might think the same (at first) that does not imply it’s the most efficient language to use with AWS Lambda. So without further ado, here we go.

I was speaking with a VP of Engineering friend at last year’s KubeCon about how to pitch Kubernetes to the C-Suite. The benefits for innovation were clear - containerized microservices empowered her small teams to deliver more value, more rapidly. As is often the case with Boardroom discussions, though, the question of cost was always next. Sure, they want you to innovate - as long as it’s within the constraints of a budget! But cost discussions around Kubernetes can be difficult.