Operations | Monitoring | ITSM | DevOps | Cloud

In a previous blog, we looked at your network operations through the lens of lean principles. We exposed the seven wastes that quietly drain your budget and burn out your teams. This constant cycle of reactive firefighting comes with a steep price. We outlined a concept in quality management known as the Cost of Poor Quality (COPQ), the total financial impact of wasted engineering hours, lost user productivity, and business risk.

Your network is not a static entity. It is a living system that has been running for years, absorbing countless changes. While your infrastructure may appear healthy on the surface, a slow and silent saboteur is often at work, methodically undermining your infrastructure from within. This is not the work of a malicious actor. It’s the inevitable result of a process you may not even be tracking: configuration drift.

Have you ever stood before a critical piece of network infrastructure, knowing it desperately needs an upgrade, yet felt a wave of paralysis wash over you? You’re not alone. It’s a common feeling when facing a project as significant as a data center migration or a move to a modern leaf-spine architecture.

Does it ever feel like your network operations team is constantly running, yet always struggling to keep up? The ticket queues are long, troubleshooting is a complex detective story, and every new application deployment adds another layer of anxiety. This constant state of reactive firefighting isn't a sign of a bad team; it's the symptom of a broken process. This operational friction, the invisible tax on every action your team takes, has a name: waste.

I want to challenge a deeply held belief in our industry, one that I once championed myself: the idea that more data is the answer. We've spent a fortune building vast data lakes of network telemetry, believing that if we could just collect everything, we would achieve a state of operational nirvana.

In the spirit of Halloween, let's talk about monsters. Not the kind that hide under your bed, but the ones that live inside your network infrastructure. For those responsible for keeping the lights on, these creatures aren't fictional; they are a daily reality. Your environment can feel like an episode from the Real Ghostbusters, teeming with things that snarl, bite, and cause chaos at the worst possible moments. Forget silver bullets; trying to fight them one by one is a losing battle.

There’s a nagging feeling of déjà vu that haunts every network operations leader. You invest significant time and resources to resolve a major performance issue. Your best engineers isolate a culprit—a misbehaving load balancer, perhaps—and after a frantic effort, service is restored. You close the ticket, confident the problem is solved. Then, two weeks later, it’s back.

Since VMware joined Broadcom, there’s been some speculation in the industry about the future of Voyence, VMware's trusted network configuration management (NCM) solution. We want to address that speculation directly and share some exciting news.

On Monday, October 20th, a significant portion of the digital services we use every day became inaccessible. For hours, banking, communication, and entertainment applications were unavailable. The root cause was later identified as a major outage within Amazon Web Services (AWS), the infrastructure that powers a vast number of online services. The initial response for any business affected by such an event is a frantic effort to diagnose the problem. Is it our application? Is our network down?

In my conversations about managing large, complex networks, one topic is now constant. The issue isn't budgets or new technology; it's about personnel. Specifically, it's the increasing difficulty of finding and retaining skilled professionals. If you are feeling this pressure, you are not alone. The search for technical talent is a universal challenge.