Operations | Monitoring | ITSM | DevOps | Cloud

A virtual desktop setup can cost more than you expect. The reason may be a few session hosts that stay active when few people need them. Others may have more capacity than their daily work requires. These costs can build up over time.

A video call freezes mid-sentence. Just for a second. Everyone waits, then carries on as if nothing happened. A week later, a new hire cannot get her laptop online in the small meeting room. She tries the next room. It works there. Nobody calls it a network problem. Not yet. It is just one of those things. Then it adds up. Two more people join. Someone plugs a printer into whatever port was free. The guest WiFi quietly starts carrying half the office because the main network keeps dropping. None of this was planned. It drifted.

We shipped a chaos feature that never caused any chaos. Our mock server has had a fault-injection effect for years with a straightforward job: withhold the response entirely and see whether the caller copes. Last week I audited it against the actual code path. It had never withheld anything. The handler returned early without writing a response. Go's net/http then did what it is designed to do, which is synthesize a 200 OK and flush the recorded body. Every experiment anybody ever ran with that effect handed the application a perfectly good answer, and every one of them passed.