Operations | Monitoring | ITSM | DevOps | Cloud

Why One Process Can Slow an Entire VDI Environment

When users report slow virtual desktops, the first instinct is often to check CPU or memory utilization. But what happens when those metrics look perfectly healthy, yet users across the environment are still complaining about slow application launches, lagging desktops and poor performance? In many cases, the bottleneck lies elsewhere. Storage is often overlooked during initial investigations, but in VDI environments it can have a disproportionate impact on the user experience.

Stop flying blind on unmanaged devices

Stop flying blind on unmanaged devices Unmanaged devices don't show up in your dashboard — until something breaks. Missing devices mean missed patches, failed audits, and incidents you never saw coming. If you can't see it, you can't fix it. In this session you'll learn how to: Discover every device on your network using SNMP Deploy the NinjaOne agent on unmanaged Windows devices directly from the dashboard — no manual legwork.

One backup policy. Every OS.

Most backup strategies look solid until someone actually needs to restore a file — and discovers the process is different for every OS. Windows, macOS, and Linux each have their own quirks, and without a consistent policy, recovery becomes a scramble. In this stream, you'll learn how to: Apply consistent file-level backup policies across Windows, macOS, and Linux Restore files and folders without hunting for the right process per device Build a single backup workflow that covers servers and endpoints.

Shipped: See what Claude Code actually costs

Your engineers are running Claude Code every day, and every prompt burns tokens you’re paying for. Until now, that spend was hard to see. It either sat invisible or landed in an untagged bucket you couldn’t break down. Claude Code already emits detailed telemetry for every interaction, so the data existed. You just had nowhere to send it that would turn it into a cost.

The three questions every CFO should be asking about AI spend

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: Sol, Terra, and Luna costs

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.

Best AI cost management tools [2026]

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.

Aiven Acquires Flow AI to Bring Agent Infrastructure Closer to Production Data

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.

5 Optimization Blockers You Didn't Know Were Inflating Your Cloud Bill

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.