Managing cloud computing costs is a big deal right now. For instance, 60% of organizations say their cloud costs are higher (over 70%) than they should be, according to our State of Cloud Cost Intelligence report. Over the last five years, several other studies have shown that controlling cloud spend is a top cloud computing challenge. Yet almost all organizations acknowledge that moving more workloads to the cloud is a top cloud initiative in the next year.

We built CloudZero for a simple reason: Bring business fundamentals to cloud-driven organizations without stifling innovation. It sounds simple, but for years, the intrinsic complexities of the cloud and extrinsic pressures to grab SaaS market share made it near-impossible for businesses to achieve this. Until CloudZero.

Your IT teams are critical to improving the efficiency of your operations and ensuring long-term business scalability. But as your organization grows and demands become more complex, the challenges of managing IT operations can become difficult, especially when managing multiple applications across various server environments. Containerization has become a popular solution for some of these challenges.

The first fifteen minutes of an incident set the tone for the rest of the resolution process. But what makes the difference between a rapid response and a stressful scramble—clear ownership—hasn't always been easy to ascertain. In this article, we’ll cover how Cortex, an internal developer portal, can be your team’s source of truth to accelerate the incident management process, and reduce MTTR.

Over the past few years, Kubernetes (K8s) has become the preferred method of orchestrating containers and microservices. Its self-healing, high scalability, and open-source nature make it appealing to a wide range of users. However, deploying, running, and scaling containerized applications and microservices with Kubernetes can be quite challenging. The Kubernetes community keeps growing, but there still aren’t that many experienced K8s engineers.

In software engineering, measuring your performance gives you the knowledge you need to make informed decisions regarding your products, features, processes, and even your dev teams. Measuring also tells you if you’re on track to meet your engineering goals. Yet, with an abundance of tasks, data, and other information to keep track of, how do you decide on the right metrics to monitor?

Recently in our Better Incidents Slack channel, there’s been some chatter around how people structure dedicated incident commanders at their company: distributed or centralized. The way I see it, there are two types of commanders: the temporary, distributed role — a hat that an on-call engineer or an engineering manager puts on during an incident. Then there’s the centralized, full-time role, where someone is the designated incident commander (or one of a few) for all incidents.