Operations | Monitoring | ITSM | DevOps | Cloud

The default cloud choice for technically literate teams has shifted. It hasn't shifted dramatically; the major hyperscalers aren't going anywhere, and their enterprise position is still strong, but the conversation that used to start with "which hyperscaler" now genuinely starts with "what do we actually need." That's new.

We are pleased to announce the release of Excel Add-ins 3.0, a major update to our Excel Add-ins for databases and cloud applications. The new version adds support for Microsoft Excel 2024 across all products. It also includes new database versions, expanded object and report support, improved data type handling, and enhanced connection security.

We’ve gotten used to understanding our applications through signals, summaries, and traces. Tiny little bits of information about how the app really works. Not because that’s the best way to do it, but because it’s been too hard to get the real thing. The real information exists. It’s on the network. How people called your app and what your code did. What other systems it called, the database queries it made, and the result sets that came back.

Trigger warning: this one is about Java, authentication, and Docker Compose files. If that is not your thing, I am sorry, but they are part of life and they are honestly not that hard to work with. Everything here is open source on our GitHub repo, so you can follow along. Recording an authenticated Java flow, replaying it, hitting the dreaded 403, and fixing it with a proxymock recommendation.

Your AI calls already emit OpenTelemetry: your LLM gateway exports it, and it’s the open standard your own services can speak. But you don’t have anywhere to turn those spans into spend you can allocate to an outcome. Now you can. CloudZero exposes an OpenTelemetry endpoint that doesn’t care what’s on the other end.

GPU utilization is one of the most expensive metrics in cloud infrastructure to get wrong. A GPU running at 30% utilization costs the same as one running at 90%, but it's doing a third of the useful work. For workloads measured in tens of thousands of GPU-hours, the difference between average utilization in the 30s and average utilization in the 70s is hundreds of thousands of dollars across the life of the workload.

We rebuilt large parts of the Qovery Console: new navigation, overviews at every level, dark mode, and a modernized frontend architecture with TanStack Router and React Suspense. Rémi is a staff frontend engineer at Qovery. He writes about frontend architecture, developer experience, and building scalable UI systems for platform engineering tools. Théo is a senior product designer at Qovery.

It's 7am. An alert fired overnight. You open your monitoring solution, navigate to the alert, cross-reference the waits, check the query plans. Twenty minutes later: it should not have fired. You knew that before you started, but you had to check anyways. The feeling of being overwhelmed by alerts is real. And so is the cost. Thresholds set once and forgotten, firing on patterns that have been normal for months. The inbox fills. DBAs learn to ignore most alerts. The workaround becomes the workflow.