Operations | Monitoring | ITSM | DevOps | Cloud

Table of Contents For most of Kubernetes’ history, memory management has been a blunt instrument. Cross your limit, and the kernel kills your container. There has been no equivalent to CPU throttling, no graceful backpressure, just a hard stop. With Kubernetes 1.37, that changes: Memory QoS, built on cgroups v2, graduates to Beta and is enabled by default.

Pop quiz: If you spend $40,000 per month on Anthropic, and you’ve got two customers, what’s your cost per customer? If you bypassed the easy answer of $20,000 and said, “Scott, you old trickster, that’s not enough information to answer that question,” you’ve won today’s prize: a lesson in the perils of average costs. Let’s flesh out the situation: You put an AI feature in your product, a document assistant powered by Claude.

We’ve released some improvements to our Azure status integration. StatusGator can now read your Azure Resource Health events via a service principal. Previously the only supported authentication mechanism was OAuth. Both pull the same data and produce the same alerts – the difference is who the connection belongs to, and what happens to it over time.

Redgate Monitor now closes that gap. You can monitor reader nodes for the first time, alongside the writer node support we already had, and get a cluster-wide view that ties node-level health back to overall cluster performance.

S3 lifecycle rules move data to Standard-IA or Glacier to cut storage cost. CloudZero now flags the buckets where that move backfires: an early delete fee is charged when an object leaves its tier before the tier’s minimum storage duration. The cause isn’t always a misconfigured lifecycle rule. A manual delete, an overwrite, or an object written straight into the tier by a replication or backup job produce the identical charge.

AI usage tracking means measuring who and what consumes AI across your company, by team, feature, and model, then converting the usage into spend and cost per unit of work. Provider consoles stop at totals per API key. Tracking puts names on those totals: which team, which product, which model, and whether any of it was worth the money. In May 2026, CNBC reported that “almost every Fortune 500 is tracking overall AI usage,” quoting ModelOp CTO Jim Olsen. The same reporting carried his warning.

Repo rightsizing is a single-pass audit of every real model call in a codebase you already shipped: SDK invocations, sub-agent dispatch sites, and agent frontmatter pins. Each call site is scored on the job it actually does, and the result commits as one blueprint file you can diff next quarter. It replaces one-skill-at-a-time reviews, which miss files where a single model key covers two different jobs.

As a product manager at Upsun with a computer engineering background, Kateryna Dvornichenko had spent months researching competing tools in the agentic development space, running tests, comparing features, and building a picture of where the market was heading. She realized the tools were impressive, but something kept standing out. "Collaboration was not the strong point of any of them," she says. "Everyone stays on their own machine with their own setup.".