Operations | Monitoring | ITSM | DevOps | Cloud

Uber ran out of its entire 2026 AI budget by April. This didn’t happen because AI technology failed, but because the company had no way to connect what it spent to what it got. The COO described it on an earnings call: “It’s very hard to draw a line” between AI usage and consumer product outcomes. And with that one sentence, we have the CFO problem of 2026.

GPT-5.6 pricing runs across three tiers, per million tokens. Sol costs $5 input / $30 output. Terra costs $2.50 / $15. Luna costs $1 / $6. All three share a 1.05 million token context window. The twist nobody priced in: OpenAI’s own system card admits Sol sometimes takes action nobody approved, then reports the job as done. For finance teams, that behavior is a governance issue worth understanding before engineering routes production traffic to it.

The best AI cost management tools in 2026 are CloudZero (best overall for connecting AI and cloud spend to business outcomes), Langfuse (best open-source LLM tracker), Portkey (best LLM gateway with cost controls), Datadog LLM Observability (best for teams already on Datadog), and CAST AI (best for Kubernetes AI infrastructure). The right tool depends on whether your primary problem is token-level LLM visibility, cloud infrastructure spend, or understanding whether your AI is generating real ROI.

Helsinki, Finland — Aiven has acquired Flow AI, a company building infrastructure for production-grade analytical AI agents. The integration of Flow AI technology will accelerate Aiven's product roadmap and make it easier for customers to securely and scalably run production AI applications and agents next to their data.

Most cloud-native cost tools are built to find and address waste reactively. Underutilized nodes, oversized requests, and idle workloads are revealed in the utilization data, the fixes are well documented, and the initial savings these tools drive are very real. But what we’ve seen consistently across clusters is a different category of blocker, one that quietly prevents consolidation and strands capacity your autoscaler can never reach. They don’t surface in dashboards as obvious waste.

A KubeVirt VM runs inside a pod. That is the trick that lets Kubernetes schedule a VM like any other workload. It also means the VM and the pod have different lifecycles. The VM is long-lived and has a stable identity. The pod is disposable. When the VM reboots, gets evicted, or live-migrates, the pod underneath is destroyed and a new one is created.

There’s a big difference between alerts generated by continuous IT monitoring and production systems and alerts that actually help people solve problems. We call those actionable alerts.

The new columnar metrics engine in Elastic Observability enables public sector IT teams to combine logging, metrics, and traces in one platform. As a result, SREs can improve uptime while protecting taxpayer dollars in the process. Public sector site reliability engineers (SREs) operate under a distinct set of pressures, whether that’s supporting a federal agency, a health department, a public university, or a transit authority.

Most CVE remediation tools can tell you that a vulnerability could be exploited. Few can confirm whether it actually is. A scanner flags the same CVE in two services and marks both as vulnerable. Only one of them ever runs the flawed code in production. That gap, reachable in theory versus reachable in fact, is the real problem, and static analysis alone cannot close it.

Organizations are increasingly using multiple models to build AI agents in order to find the best balance of performance and cost for each agentic task and LLM call. As we discovered in the 2026 State of AI Engineering report, there isn’t currently a clear winner in terms of adoption among competing models and many organizations are keeping older models in flight despite frequent new releases.