Operations | Monitoring | ITSM | DevOps | Cloud

Runbooks are rarely missing because teams don't value them. They're usually missing because incident response, follow-up, and platform work compete for the same limited time. By the time an issue is resolved, the knowledge is fresh, but the window to document it is already closing. That gap creates familiar failure modes: over-reliance on senior engineers, slower handoffs, and less confidence for whoever is on call next.

Not long ago, adding a new cost connector to CloudZero was a serious undertaking. We’d task multiple engineers, build in extended review cycles, run a private preview period. But a single connector could take up to two months from kickoff to customer hands. For the major cloud providers, that timeline was acceptable. The size of the investment matched the scale of the integration. But the tools landscape has changed. Our customers’ teams don’t just run on AWS and Azure.

The Zephyr west tool is a powerful workspace manager, but it is admittedly pretty feature-rich: there’s a lot of functionality buried inside that tool! I thought it would be interesting to share a few tips and tricks that I use with west to make my Zephyr development workflow a little smoother.

The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards.

Regular DR testing is no longer a compliance checkbox — it is a critical engineering discipline that determines whether an organisation can survive a real cloud outage with its services and revenue intact. As the AWS Middle East incident demonstrated, regional cloud failures can strike without warning and defeat standard redundancy models, making untested DR plans dangerously unreliable.

On April 1st, I joined Akshay Utture from Augment Code for a webinar on how AI agents use production feedback to improve code.

Autonomous IT is the result of a long operational evolution, from static monitoring and rule-based automation to AIOps and now to systems that can increasingly diagnose, prioritize, and act within defined guardrails. Autonomous IT gets talked about like it appeared out of nowhere. As if someone flipped a switch and suddenly systems started managing themselves. The reality is far less dramatic and far more instructive. What we’re seeing today is the result of decades of incremental progress.

Effective network monitoring requires path validation, not only device polling. Traditional Network Monitoring System (NMS) tools were built for static networks, not today’s hybrid reality. You poll devices, check interface counters, and still struggle to explain why users complain about latency. Traffic moves across SD-WAN architectures, cloud routing layers, and public internet paths that device metrics never capture.

Fragmentation limits AI automation because context is split across systems, forcing humans to bridge the gap. Most IT environments are fragmented by design. Observability data lives in one set of systems, investigation happens in another, and execution sits behind separate tools with their own ownership and controls. During an incident, context does not move with the work.