Why are Monitoring and Management never included?

Many small to mid-sized companies invest heavily in differentiated business services that allow them to compete against larger rivals. But in many cases, not as much consideration goes into planning how to monitor the IT infrastructure that supports those services. When it comes to spending money, the first priority is designing and implementing applications, not designing the monitoring solutions for those applications. I have worked on several virtualization projects over the last couple of years and for most customers the key driver is REALIZING TANGIBLE CAPEX AND OPEX COST SAVINGS.

The question is once you have realized these cost savings, how do you manage this new infrastructure. Virtualization shifts the paradigm from managing “the raw ingredients of IT”, i.e.  Physical Server running an OS to managing CPU and memory across a group of physical servers as a uniform shared pool of resources.

Innovations such as virtualization allow smaller organizations to improve utilization of their limited IT resources and budget. However, many companies do not realize the promised savings because the added complexity of the IT environment adds to their monitoring costs. For example, an application modernization initiative. Typically the project is tied directly to revenue therefore the first priority which is designing and implementing applications consumes the budget, leaving monitoring in the background until a critical outage occurs.

Overall, deploying an efficient and effective monitoring solution is often perceived as a long and complex process, especially if little to no subject matter expertise exists within the organization around particular applications or IT components. Add to that the perception that a monitoring solution is expensive and odds are that it never gets implemented.

It really isn’t that complicated, check out this three minute video;