Operations | Monitoring | ITSM | DevOps | Cloud

When CloudZero CTO Erik Peterson joined the SourceForge podcast in January 2026, he didn’t just talk about cloud costs. He reframed them as a launchpad for innovation, survival, and competitive advantage. Whether he was describing the “trough of lost innovation,” the “freemium tax,” or why efficiency is the next frontier of engineering culture, Erik’s expert insights go beyond FinOps hygiene.

In the last article in this series, we explored how IT professionals and leaders can cut through the hype surrounding agentic AI and gain a deeper understanding of what the technology actually offers. Now, we turn to the practical side: how to integrate it effectively. Let’s explore the challenges and outline strategies that organizations of all sizes can use to adopt agentic AI with confidence.

Enterprise software has moved past the generative AI testing phase. Businesses with millions of daily users or workloads are no longer just prototyping LLMs in a vacuum. They’re directly wiring agentic efficiency into product interfaces and infrastructure to stay competitive. This wave is often compared to the spread of microservices in the past, but we aren’t just adding new dependencies and complexity.

The difference between an AI assistant that "almost" works and one that consistently delivers high-value results is rarely a matter of raw model capability. Instead, the bottleneck is typically the quality and structure of the instructions provided. For DevOps and SRE teams building automated workflows, "magical prompt tricks" are no substitute for a repeatable, engineered structure.

We have spent the last decade engineering our organizations for velocity. We optimized for "Land and Expand." We celebrated bookings. We built commercial architectures designed to intake revenue faster than we could operationalize it. In that era, operational friction was accepted as the cost of doing business. That era is over. The mandate has shifted from growth at all costs to efficient growth.

This report covers the operational status of major AI systems during December 2025, including Anthropic, Cohere, DeepSeek, Google Gemini, Groq Cloud, OpenAI, Perplexity, Replicate, and xAI. The data encompasses official incidents reported by providers and monitoring insights from IsDown's detection system.

Consider this: traditional cloud cost monitoring was like checking your fuel gauge once a month — after the trip was already over. That model worked when infrastructure scaled slowly. You provisioned resources predictably and paid for stable, linear usage. AI breaks that model. Today, AI costs behave like a high-performance engine with a hypersensitive throttle. A small input, like a prompt change or a single power user, can dramatically increase your fuel burn in seconds.

At Honeycomb, we’ve been using Claude Code across our engineering team for a while. Anecdotally, I had a sense of who the power users were, and I had seen some examples of complex usage. But I wanted to be able to confidently answer questions, like: Claude Code supports OpenTelemetry out of the box, which means sending telemetry to Honeycomb takes just a few minutes of configuration.