Monitoring is a lot of work. A monitoring system is a service unto itself, and like other applications it needs care, feeding, configuration, databases, DBAs, patching, and maintenance. Though it often prevents the loss of revenue, it doesn’t generate revenue except in rare circumstances. Last, it requires vigilance and attention to detail that is often overlooked or impossible in a busy IT environment. So why even bother?
There’s a common misconception in the IT industry. This misconception stems from the premise that the premises of your infrastructure will either be more expensive or less expensive based on its location. Okay, that may sound like a lot of metaphorical jibber jabber and mixed-speak, but that’s how the industry talks when backed into a corner.
I think we’ve all had that moment at 3:00 a.m. over the weekend when we wish our monitoring and management systems would just shut up. The UPS in rack 4’s battery life is at 40%, we GET it. But we’ve also had that moment when we tilt our head a bit looking at a monthly availability report with service gaps and can’t recall ever seeing a critical alert that telepresence went down on the executive wing.
Earlier this year I had the opportunity to speak at VMWorld in San Francisco. The session title was “Using Virtual SAN to Maximize Database Performance”, and in that session I spent time focusing on performance as well as recovery. Why would recovery be a part of the talk? Because: