Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Cloud monitoring, security and related technologies.

Engineer Cloud Cost Awareness: Why It Fails & Fixes | Harness Blog

Engineers often ignore cloud costs due to lack of visibility, misaligned incentives, and disconnected workflows. This guide explores the root causes and provides actionable strategies to embed cost awareness into engineering culture, including automation, real-time feedback, and FinOps best practices that make cost optimization a natural part of the development process.

Why workflows, not agents, are the primitive your team is missing

If your team has adopted AI coding agents, you've probably noticed something strange: writing code stopped being the hard part. That's the shift Patrick, a principal engineer at Upsun, kept returning to in our latest Product Highlights conversation. He's spent twelve years here, most of them writing back-end APIs in Go, and the past year building with AI on our newest product, Upsun Dispatch. His verdict on where the bottleneck moved is blunt: "The code isn't really a problem anymore.

Don't Trust the Diff: Making AI-Generated Code Reviewable And Maintainable

Coding agents changed implementation economics faster than they changed confidence. They let us produce more code, more quickly, but they did not make reviewers any better at understanding system-wide consequences. In our Kubernetes automation stack, that gap became impossible to ignore once AI started generating meaningful amounts of controller code.

Why workflows, not agents, are the primitive your team is missing - Product Highlights

AI helped your engineers ship more code. It didn't help your team ship more product. So where did the bottleneck actually go? In this Product Highlights conversation, Patrick—a principal engineer at Upsun with twelve years building back-end APIs in Go—breaks down what changed once AI agents entered the workflow. His take: "The code isn't really a problem anymore. We can write that really fast. Everything else is still a bit behind the code." We get into.

Why Cloud Security Pays Off: Key Benefits Explained for Decision-Makers

Every new app, user, workload and connection creates value, yet it can also create another opening for disruption. One weak password, a missed update or an exposed setting can lead to downtime, lost data and difficult questions from customers and leadership. For decision-makers, the issue is not whether cloud security costs money. It is whether the business can afford the cost of operating without proper safety. Powerful cloud security helps you reduce risk, improve visibility, support compliance and give teams the trust to grow without looking over their shoulders.

AI ROI is not an engineering metric

I spend most of my week talking to companies about AI ROI. A few months ago, that was still a weirdly specific conversation. Now it’s everywhere. CloudZero spends a lot of time in that conversation, so I’m glad the market is talking about it. But the conversation tends to start, and stall, in the wrong place. There are two ideas I keep coming back to: That doesn’t mean developer productivity is fake. It’s very real.

The real cost of your dependency on hyperscalers

There's a version of cloud strategy that looks like a decision and a version that looks like drift. Most enterprises are living the second version. AWS won an early workload because the team knew it. Azure followed the Microsoft enterprise agreement. GCP came in through a data science team that preferred its ML tooling. Nobody chose concentration; it just accumulated.

Shipped: Allocate AWS cost by account name, not account ID

Until now, allocating by account name meant doing the work yourself: hand-building a custom dimension that mapped every twelve-digit AWS ID to a readable name, then maintaining it by hand in CostFormation. That mapping is fragile. Rename a definition or edit the wrong line and dashboards that depended on it quietly break. Now the account name is built in for accounts connected through AWS CUR 2.0.