Operations | Monitoring | ITSM | DevOps | Cloud

CloudZero’s research has determined that as many as 60% of SaaS business leaders feel their cloud spend is higher than it should be. Considering cloud spend is a dominant portion of a SaaS company’s operating costs, unexpectedly high cloud bills can be a significant problem. While many SaaS leaders use discount plans to stem the bleeding, we believe the better solution lies with giving your engineers the tools to track and optimize costs as they build.

Reviewing the Current State of Infrastructure as Code (IaC), its Challenges, the Emergence of Crossplane, Adoption Difficulties, and the Road Ahead! Infrastructure as code (IaC) has become an indispensable practice for managing and deploying cloud-native applications. By defining infrastructure through code, developers can efficiently and consistently manage their infrastructure. In this post, we’ll delve into the state of IaC, the problems it poses, and the new approach offered by Crossplane.

Delivering seamless digital experiences is a top priority for every business today. However, the IT infrastructures that fuel these experiences are getting increasingly complex. The rapid adoption of technologies like containerization, microservices, and cloud and serverless computing, along with traditional infrastructure, is creating increasingly hybrid and distributed IT ecosystems, making it a challenge for organizations to manage them effectively.

You may be thinking of investing in multiple cloud vendors to increase redundancy and deal with the complexity of your enterprise requirements. You are not alone. Many enterprises are moving in this direction to take advantage of the options offered by competing cloud vendors. Adopting one major cloud vendor is a complex project that can consume a company for months if not years.

The old saying goes, “practice what you preach.” When Ivanti started its "Customer Zero" initiative, Bob Grazioli, Chief Information Officer, saw it as a perfect opportunity to test the products and services consumed by customers. For example, during Ivanti’s move to the cloud, Grazioli and the team experienced the same issues that customers would’ve experienced in their migration process. This first-hand experience allowed them to make improvements along the way.

As Kubernetes continues to gain popularity as a container orchestration system, mastering its command-line interface becomes increasingly vital for DevOps engineers and developers alike. Kubectl, the Kubernetes command-line tool, is an essential component in managing and deploying applications in a Kubernetes cluster. This tool allows you to interact directly with the Kubernetes API server and control the state of your cluster.

In my previous articles, I discussed how to design considerations for observability solutions and how observability can augment your security implementation. In this article, I will discuss how an observability solution can provide valuable insights into your business operations through the collected data from various systems, applications, and services.

With the surge in digitization, the concept of cloud migration has become a fundamental reality for many organizations. VMware, a widely accepted leader in server virtualization, has enabled many businesses to take advantage of virtual machines’ benefits. However, as businesses evolve, so do their requirements. This often leads to the need for moving these VMware-based virtual machines to more flexible and scalable platforms like Microsoft Azure.

InfluxDB Cloud 3.0 is a versatile time series database built on top of the Apache ecosystem. You can query InfluxDB Cloud with the Apache Arrow Flight SQL interface, which provides SQL support for working with time series data. In this tutorial, we will walk through the process of querying InfluxDB Cloud with Flight SQL, using C++. The C++ Flight SQL Client is part of Apache Arrow Flight, a framework for building high-performance data services.

People seem to struggle with the idea that there are no repeat incidents. It is very easy and natural to see two distinct outages, with nearly identical failure modes, impacting the same components, and with no significant action items as repeat incidents. However, when we look at the responses and their variations, we can find key distinctions that shows the incidents as related, but not identical.