The focus on applications often gets lost in the shuffle when implementing virtualization which is unfortunate because if you look at any server environment its sole purpose is really to serve applications. No matter what hardware, hypervisor or operating system is used, ultimately it all comes down to being able to run applications that serve a specific function for the users in a server environment. When you think about it, without applications we wouldn’t even have a need for computing hardware, so it’s important to remember, it’s really all about the applications.

So with that I wanted to provide 5 tips for monitoring applications in a virtual environment that will help you ensure that your applications run smoothly once they are virtualized.

Tip 1 – Monitor all the layers

The computing stack consists of several different components all layered on top of each other. At the bottom is the physical hardware or bare metal as it is often referred to. On top of that you traditionally had the operating system like Microsoft Windows or Linux, but with virtualization you have a new layer that sits between the hardware and the operating system. The virtualization layer controls all access to physical hardware and the operating system layer is contained within virtual machines. Inside those virtual machines is the application layer where you install applications within the operating system. Finally you have the user layer that accesses the applications running on the virtual machines. Within each layer you have specific resource areas that need to be monitored both within and across layers. For example storage resources which are a typical bottleneck in virtual environments need storage management across layers so you get different perspectives from multiple viewpoints.

To have truly effective monitoring you need to monitor all the layers so you can get a perspective from each layer and also see the big picture interaction between layers. If you don’t monitor all the layers you are going to miss important events that are relevant at a particular layer. For example if you focus only on monitoring at the guest OS layer, how do you know your applications or performing as they should or that your hypervisor does not have a bottleneck. So don’t miss anything when you monitor your virtual environment, you should monitor the application stack from end to end all the way from the infrastructure to the applications and the users that rely on them.

Tip 2 – Pay attention to the user experience

So you monitor your applications for problems but that won’t necessarily tell you how well it’s performing from a user perspective. If you’re just looking at the application and you see it has plenty of memory and CPU resources and there are no error messages you might get a false sense of confidence that it is running OK. If you dig deeper you may uncover hidden problems, this is especially true with virtualized applications that run on shared infrastructure and multi-tier applications that span servers that rely on other servers to properly function.

The user experience is what the user experiences when using the application and is the best measure of how an application is performing. If there is a bottleneck somewhere between shared resources or in one tier of an application it’s going to negatively impact the user experience which is based on everything working smoothly. So it’s important to have a monitoring tool that can simulate a user accessing an application so you can monitor from that perspective. If you detect that the user experience has degraded many tools will help you pinpoint where the bottleneck or problem is occurring.

Tip 3 – Understand application and virtualization dependencies

There are many dependencies that can occur with applications and in virtual environments. With applications you may have a multi-tier application that depends on other services running on other VMs such as a web tier, app tier and database tier. Multi-tier applications are typically all or nothing, if any one tier is unavailable or has a problem the application fails. Clustering can be leveraged within applications to provide higher availability but you need to take special precautions to ensure a failure doesn’t impact the entire clustered application all at once. This may also extend beyond applications into other areas, for example if Active Directory or DNS is unavailable it may also affect your applications. In addition there are also many dependencies inside a virtual environment. One big one is shared storage, VMs can survive a host failure with HA features that bring them up on another host, but if your primary shared storage fails it can take down the whole environment.

The bottom line is that you have to know your dependencies ahead of time, you can’t afford to find them out when problems happen. You should clearly document what your applications need to be able to function and ensure you take that into account in our design considerations for your virtual environment.  Something as simple as DNS being unavailable can take down a whole datacenter as everything relies on it. You also need to go beyond understanding your dependencies and configure your virtual environment and virtualization management around them. Doing things like setting affinity settings so when VMs are moved around they are either kept together or spread across hosts will help minimize application downtime and balance performance.

Tip 4 – Leverage VMware HA OS & application heartbeat monitoring

One of the little known functions of VMware’s High Availability (HA) feature is the ability to monitor both operating systems and applications to ensure that they are responding. HA was originally designed to detect host failures in a cluster and automatically restart VMs on failed hosts on other hosts in the cluster. It was further enhanced to detect VM failures such as a Windows blue screen by monitoring a heartbeat inside the VM guest OS through the VMware Tools utility. This feature is known as Virtual Machine (VM) Monitoring and will automatically restart a VM if it detects the loss of the heartbeat. To help avoid false positives it was further enhanced to detect I/O occurring by the VM to ensure that it was truly down before restarting it.

VMware HA Application Monitoring was introduced as a further enhancement to HA in vSphere 5 that took HA another level deeper, to the application. Again leveraging VMware Tools and using a special API that VMware developed for this you can now monitor the heartbeat of individual applications. VMware’s API allows application developers for any type of application, even custom ones developed in-house to hook in to VMware HA Application Monitoring to provide an extra level of protection by automatically restarting a VM if an application fails. Both features are disabled by default and need to be enabled to function, in addition with application monitoring you need to be running an application that supports it.

Tip 5 – Use the right tool for the job

You really need a comprehensive monitoring package that will monitor all aspects and layers of your virtual environment. Many tools today focus on specific areas such as the physical hardware or guest OS or the hypervisor. What you need are monitoring tools that can cover all your bases and also focus on your applications which are really the most critical part of your whole environment. Because of the interactions and dependencies with applications and virtual environments you also need tools that can understand them and properly monitor them so you can troubleshoot them more easily and spot bottlenecks that may choke your applications. Having a tool that can also simulate the user experience is especially important in a virtualized environment that has so many moving parts so you can monitor the application from end-to-end.

SolarWinds can provide you with the tools you need to monitor every part of your virtual environment including the applications. SolarWinds Virtualization Manager coupled with Server & Application Monitor can help ensure that you do not miss anything and that you have all the computing layers covered. SolarWinds Virtualization Manager delivers integrated VMware and Microsoft Hyper-V capacity planning, performance monitoring, VM sprawl control, configuration management, and chargeback automation to provide complete monitoring of your hypervisor.

SolarWinds Server & Application Monitor delivers agentless application and server monitoring software that provides monitoring, alerting, reporting, and server management. It only takes minutes to create monitors for custom applications and to deploy new application monitors with Server & Application Monitor’s built-in support for more than 150 applications. Server management capabilities allow you to natively start and stop services, reboot servers, and kill rogue processes. It also enables you to measure application performance from an end user’s perspective so you can monitor the user experience.

With SolarWinds Virtualization Manager and SolarWinds Server & Application Monitor you have complete coverage of your entire virtual environment from the bare metal all the way to the end user.

…because I actually got a VMworld session approved!  I last had a VMworld session approved (2 of them) in 2010 for my Deep Dive on Virtualization and Building a Home Lab sessions. I’ve really given up hope in recent years of getting another one due to the sheer number of submissions and because VMware has so many sessions because there product offerings are so broad now. This year I had one of the sessions that I submitted through HP “The Top 10 Things you MUST know about Storage for vSphere” approved, it is based on a presentation that I built for our VMUG user conference sponsorship’s this year. As part of HP’s sponsorship we were guaranteed a few session slots but my session made it on its own outside of those slots. So thank you to all who voted for my session and I look forward to seeing you at VMworld.

Gartner just released their annual “Magic Quadrant for x86 Server Virtualization Infrastructure” report for 2013 and Microsoft continues to draw closer to VMware’s top position. If you look at the differences over the years VMware pretty much hasn’t moved and remains near the highest position that you can be in the quadrant as they lead in both their ability to execute and completeness of vision. That should really come to no surprise as VMware still is and always has been the market leader and have set the bar high in the x86 virtualization field. But Microsoft is slowly but surely closing the gap, I’d be surprised if they ever pass VMware in either of the directions given VMware’s lightning focus on virtualization, but I think they are close enough for most companies to take Microsoft seriously. Also to note the niche players are still mostly niche players and will most likely remain there for the foreseeable future as VMware & Microsoft dominate the x86 virtualization playing field. Citrix isn’t really doing much on the server virtualization side anymore and a large percentage of their client virtualization installations are on non-Citrix server hypervisor platforms like vSphere.

Last year the VMUG leaders in Phoenix invited me to present their keynote at the annual Phoenix VMUG User Conference. I love VMUG’s but had to turn it down unfortunately because of conflicts and having to travel there from Denver. Well I felt bad about having to do that so I ended up just recently moving from Denver, CO to Phoenix, AZ so I could be available to do it if they asked again this year. So as a result I’ll be speaking at the Phoenix VMUG this year which takes place on Thursday, July 11th at the Desert Willow Conference Center in Phoenix. I believe I’ll be doing the morning keynote which will be based on a deck that I will be presenting at VMworld this year for a session that was approved titled “Top 10 things you MUST know about storage for vSphere”. So if you’re in the Phoenix area make sure you head on over to the VMUG website and register. I look forward to meeting my fellow VMware geeks in the valley and participating in the VMUG community here.

Having largely perfected the server side of virtualization, VMware & Microsoft have turned their attention towards improving storage as they recognize the critical role that it plays in a virtual environment. VMware in particular has put a big focus on enhancing storage features in recent vSphere releases and promises to continue that trend in future releases. To understand why storage is getting so much attention now you need to look at the role storage plays in a virtual environment.

If you look at the four basic resources that are required for a VM to function, CPU, memory, network and storage; storage is different from the other resources in two ways. First, the other resources are all local to a host and storage is typically accessed remotely via a network or fabric and I/O has a long journey from the host to a storage device. Secondly, unlike the other resource types, storage is a shared resource by many hosts so there is a lot of contention for it. As a result storage is often the limiting factor to achieving higher VM densities which is why VMware has put so much focus on storage features.

Looking at some recent storage enhancements, there are a few key areas that VMware & Microsoft are focusing on that include integration, management and software defined storage. VMware has been trying to mimic with software many of the features traditionally found inside storage arrays and has also turned towards mimicking an entire array with a virtual storage appliance. Let’s take a look at the top 5 storage enhancements from VMware & Microsoft and their use cases in a virtualized environment.

1 – Storage APIs and integration

Integration between the hypervisor and storage devices is the key to efficiency in a virtual environment. This allows the two to communicate with each other more effectively and also offloads resource intensive tasks from the hypervisor to the storage array which is better equipped to handle them. VMware has a number of APIs that they have developed under the vStorage API family that allow storage vendors to integrate directly with vSphere. The vStorage APIs for Array Integration (VAAI) provide capabilities such as offloading block zeroing and data copy as well as providing a more granular disk locking mechanism. VMware has made enhancements to VAAI to improve thin provisioning management and efficiency by allowing the hypervisor to reclaim disk blocks once data has been deleted. Microsoft has made improvements in this area as well with their Offloaded Data Transfer (ODX) and thin reclaim (UNMAP) capabilities that are built into Hyper-V & Winders Server.

2 – Storage resource controls

Because storage is a shared resource, contention for storage resources can be like the Wild West with many hosts and VMs all fighting over limited storage resources. Having a sheriff in town can help tame that contention and ensure that VMs are getting the resources they need. Features like VMware’s Storage I/O Control (SIOC) allows for centralized storage resource management so storage prioritization can be applied across all hosts connected to a datastore instead of on an individual basis. This can help ensure fairness across hosts so critical VMs get the storage resources they need and you don’t have to worry about one host hogging all the storage resources.

3 – Non-disruptive storage migration

A virtual environment is very dynamic and VMs need mobility to ensure resources are balanced and for increased availability. VMware has had their vMotion feature for years that allows a VM on shared storage to move from one host to another when needed without any disruptions. Microsoft introduced a similar feature which they call Live Migration in Hyper-V 3.0, but unlike vMotion it did not require shared storage. VMware enhanced vMotion when they introduced Storage vMotion which allows a VM to move from one datastore to another without disruption. vMotion and Storage vMotion were two different features that operated independently and at different levels (host vs. storage). VMware finally bridged the gap between the two features in vSphere 5.1 with their latest enhancement informally called “Shared Nothing vMotion” that can move a VM to a different host and datastore in one operation. This was on par with what Microsoft had with Live Migration and provides better VM mobility especially for environments that do not have shared storage and can help make balancing workloads and shifting VMs around for scheduled maintenance much easier.

4 – Virtual Storage Appliances

Virtual storage appliances (VSA) allow you to create a virtual shared storage device from local server disk that can be presented to any host and used in the same manner as traditional physical shared storage (NAS/SAN). While historically known as VSAs, VMware has created a new marketing term for them called Software Defined Storage that is part of their whole Software Defined Data Center vision. Today there are many VSAs on the market both from VMware and other storage vendors that offer different features and capabilities. Microsoft currently does not offer a VSA as part of Hyper-V but there are some 3rd party VSA’s that work with Hyper-V. VSAs can provide many benefits and are suited for many different uses cases. They are great for SMBs that desire shared storage to be able to use the many advanced virtualization features that required shared storage but don’t have the budget for a NAS or SAN device. They are also good for remote office deployments and to implement cost-effective BC/DR.

5 – Storage load balancing

Storage workloads are often very dynamic and unpredictable and being able to shift them around to better balance them helps improve performance and avoid overburdened datastores. VMware has a feature called Storage Distributed Resource Scheduler (DRS) that allows for intelligent placement of VMs that are powered on as well as the shifting of workloads from one storage resource to another whenever needed to ensure optimum performance and eliminate I/O bottlenecks. Storage DRS is similar to the auto tiering feature that is found in storage arrays but instead of working at the disk block level it works at the VM level. Storage DRS works in conjunction with other vSphere storage features, when combined, Storage DRS is the brains, Storage vMotion is the muscle and Storage I/O Control is the judge to help create a more balanced and efficient storage platform for VMs.

As the hypervisor management tools take over and automate more and more tasks, it becomes harder to maintain visibility between the virtual and storage resources. As a result, having good virtualization management and monitoring software for your virtualization and storage resources is critical. Because storage is such an important part of a virtual environment you can’t afford to make any assumptions about your storage resources. Products like SolarWind’s Virtualization Manager and Storage Manager can help you proactively monitor and analyze the performance and capacity of your storage resources. Featuring configurable real-time dashboards you can easily stay on top of storage trends and identify any problem areas that may be occurring. Together, SolarWinds Virtualization Manager and Storage Manager can help you keep a sharp eye on the performance and capacity of your entire physical and virtual storage infrastructure-from VM to spindle!