Operations | Monitoring | ITSM | DevOps | Cloud

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

Sponsored Post

Building a Modern Cloud Outage Response Workflow in Slack and Microsoft Teams

On May 7 and 8, 2026, a thermal event in a single AWS data center hall knocked out power to EC2 instances and EBS volumes in a single Availability Zone in us-east-1. Within hours, more than 150 cloud services went down, including Coinbase, Reddit, HubSpot, and Atlassian's suite of tools, Jira, Confluence, and Trello among them. For teams without a structured cloud outage response workflow, the next several hours looked familiar: Slack DMs asking "is it down for you too?", tab-switching between status pages, and incident commanders repeating the same update in three different channels.

Why Config Changes Cause Most Cloud Outages in 2026

If you have watched the incident channels light up over the past few weeks, you already sense the theme of 2026: cloud outages are no longer rare, dramatic once a year events. They are a steady drumbeat, and most of them trace back to the same root cause. Not a data center fire, not a rogue backhoe severing a fiber line, but a routine configuration change that went out, behaved differently than expected, and cascaded.

Why Cloud Cost Visibility at Scale Fails (And How to Fix It) | Harness Blog

Cloud cost visibility at scale usually works great… until it suddenly doesn’t. At first, everything feels manageable. You can track spend by service. You know which team owns which resources. Reports are clean, and the numbers make sense. Then one day, there’s a $47,000 spike spread across three AWS accounts that no one noticed for eleven days. Leadership wants answers. Engineering wants context. And your carefully designed tagging strategy?

Azure Virtual Desktop Monitoring: Challenges, Metrics & Best Monitoring Solutions

Azure Virtual Desktop (AVD) is rapidly growing in popularity as modern way to deliver virtual desktops and apps to users, with Azure providing the infrastructure as alternative to on-prem VDI environments. As organizations expand their use of AVD in Azure, monitoring becomes critical.

Agent security starts with where the agent runs, not how it behaves

When engineering teams evaluate AI agents, the first questions are usually about capability. Which model performs best? How much faster can it write code? What's the return on investment? Security, if it enters the conversation at all, tends to come later. Patrick Dawkins, Principal Software Engineer at Upsun, thinks that's backward. Over the past year, he's been building the infrastructure that enables AI agents to operate safely within engineering teams.

Railway Mania, the birth of the S&P 500, and the lesson for the AI era

In 1846, Britain poured roughly 7% of its national income into railways, proportionally about three times what the U.S. spends on AI infrastructure today. The technology delivered everything it promised, and a generation of investors still lost their shirts. What sorted the winners from the wreckage wasn't conviction about the technology; it was whether ROI was measured or asserted. The man who fixed that problem gave his name to the S&P 500.

AI cost reduction: tactics that preserve performance

AI cost reduction means lowering what you spend to run AI (tokens, inference, and compute) without sacrificing quality. The highest-leverage tactics, prompt caching, batching, and routing easy work to smaller models, cut spend 50 to 90% by removing waste, not capability. Somewhere right now, a finance leader is opening an AI bill that has quietly tripled, with no new product to show for it. Nobody approved it. No single decision caused it.

Shipped: Put every AI task on the cheapest model that can actually do it

If your team builds with AI, someone is defaulting to the biggest model available (say, Fable) because it feels like the safe pick, and the safe pick is almost always the most expensive one. One over-powered choice looks harmless on its own, but multiplied across every prompt, agent, and workflow, and you get a big number on the P&L. All that, yet nobody chose which model on purpose. As we like to say, using a default is not a decision.