Operations | Monitoring | ITSM | DevOps | Cloud

Despite the enterprise-wide pivot toward digital deflection, voice remains the primary escalation channel for high-complexity customer issues. Yet, while organizations rigorously optimize digital touchpoints, telephony frequently remains a siloed legacy endpoint, disconnected from the broader CRM architecture. This integration gap creates a strategic blind spot that fundamentally undermines your digital roadmap.

History is everywhere at Dartmouth College, and while the campus is steeped in tradition, its IT infrastructure can’t afford to get stuck in the past. In an institution where world-class research and undergraduate studies intersect, technology must be fast, invisible, and – above all – reliable. That reliability was put to the test when Dartmouth’s load balancing vendor was acquired twice in five years, as Avi Networks moved to VMware and VMware moved to Broadcom.

Grafana Assistant is the most general-purpose tool we’ve delivered since dashboards. People use our Grafana Cloud LLM to understand unfamiliar areas of their stacks, generate dashboards and beautiful visualizations out of thin air, build queries, and support investigations.

Note: This blog post originally published in May 2025 and was updated in February 2026 to reflect that Git Sync is now available in public preview in Grafana Cloud. As your Grafana instance scales, so does the challenge of maintaining dashboards. Managing dozens—or hundreds—of dashboards through the UI alone can quickly become overwhelming. Tracking changes gets murky, dashboards multiply, and consistency suffers.

When I joined Kubex last year, the company was already well aware of the growing power of Large Language Models. As a company focused on intelligent resource optimization for Kubernetes, GPUs, and cloud infrastructure, generative AI didn’t feel like a threat so much as a natural extension of where the industry was heading. Kubex had already invested heavily in machine learning, but it was becoming clear that foundation models could unlock an entirely new class of capabilities for our customers.

Organizations are starting to question whether the value they get from traditional Network Monitoring Systems (NMS) justifies the budget they’ve locked into them.

When Anthony Leung talks about FinOps, he’s speaking from operating at real scale — not theory. As VP of Engineering Platforms and Security Research at Forcepoint, he led a transformation that cut cloud spend in half while improving availability, and built a culture where engineers own their economics.

AI is the new frontier for FinOps maturity. It introduces fresh spend patterns and new opportunities for value. As GPUs, inference, and retraining reshape costs, FinOps maturity grows through visibility, forecasting, and shared mindset about how these workloads drive business impact. In this 2025 post, I gave my guidelines for implementing AI tagging to give business context and clarity to vague AI invoices. Now, I’m sharing the next level up: how to drive FinOps in AI with AI.

Here’s the uncomfortable truth: most companies do not have an AI problem. They have a delivery problem wearing an AI costume. MIT’s Project NANDA research has been widely cited for a brutal headline statistic: roughly 95% of corporate generative AI pilots fail to produce measurable business impact or returns, while only about 5% break through to meaningful outcomes. (Yahoo Finance) The models are impressive. The demos are dazzling. The budgets are real.

Deployments are one of the few moments where software development still feels risky. Teams may have tests, a staging environment, and careful review processes, yet the final step still carries uncertainty. Will this change behave the same way in production? Will it interact cleanly with existing data, traffic, and infrastructure? Will it introduce regressions no one anticipated? Preview environments exist to reduce that uncertainty.