|
|
|
VMware virtual server technologies provide companies with the ability to do more with less resources. While this technology makes computing easier and efficient, virtualization makes IT infrastructures harder to monitor and manage. Effective monitoring and management is critical for these environments to be adequate replacements for traditional hardware-based infrastructures.
The eG Monitor for VMware® InfrastructuresTM (the eG VM MonitorTM), part of the eG Enterprise Suite, is a comprehensive solution for monitoring and managing all aspects of virtual hosts and guests, whether the infrastructure is used to support server or desktop applications. Coupled with the ability of the eG Enterprise Suite to monitor over 80 applications, including Citrix, Microsoft, Oracle, IBM, SAP, and others, the eG VM Monitor - with its patent-pending In-N-Out MonitoringTM technology -- provides a comprehensive end-to-end solution for monitoring and managing the performance of virtual IT infrastructures.
Administrators can use the eG VM Monitor to monitor the performance of their physical and virtual infrastructures, troubleshoot problems to determine where the root-cause lies, assess where capacity bottlenecks are, and plan the usage of their servers and applications to optimize the utilization of the physical and virtual resources. The key customer benefits of this solution include higher uptime, better end-to-end performance, and operational cost savings through more effective utilization of key IT staff. |
|
Multi-tier IT infrastructures are a nightmare to troubleshoot because of the dependencies that exist between application tiers. For instance, a failure in the database tier could result in slow downs in the application and web server tiers. Hence, monitoring solutions that view the infrastructure as independent silos cannot effectively monitor and diagnose problems in such infrastructures. The addition of virtualization to such infrastructures makes monitoring and management of these infrastructures even more challenging!
 |
Fig 1: A problem in one application can affect all the other applications involved in the service delivery. |
 |
 |
Fig 2: Excessive disk reads by the media server slow down Oracle database accesses |
Since a single VMware® vSphere/ESX Server is used to host multiple virtual machines (VMs), a single malfunctioning application on a VM can degrade the performance seen by applications hosted on the other VMs. Figures 1 and 2 illustrate such an example. In this scenario, users are experiencing slowness in their access to a web-based service. From the service topology, it is clear that the database server is the cause of the slowdown. Figure 2 illustrates that since the database server is hosted on the same vSphere/ESX server as a media server, high I/O activity due to increased access to the media server is resulting in the database server seeing slow disk accesses. To accurately diagnose the problem in this example, a monitoring solution must not only consider the inter-dependencies between applications that are involved in service delivery, but it must also consider the existential relationships between applications, virtual machines, and physical machines. Besides resource contention among guest virtual machines, applications executing on the vSphere/ESX service console can also affect the performance of the virtual infrastructure.
While knowing which VM is consuming excessive resources is helpful, it is even more important to understand whether the VM's behavior is normal. For instance, a memory leak in one of the applications executing inside a VM may be causing the VM's memory usage to increase over time. In such cases, it is essential that the monitoring solution be able to look in-depth into each guest VM and detect abnormalities. While deploying individual agents inside each VM provides this level of visibility, this can result in additional resource overhead, licensing fees, and maintenance cost.
Performance degradations in a virtual infrastructure may also be because a virtual machine has not been configured with sufficient resources to handle its workload. A monitoring solution must be able to differentiate problems resulting from inadequate virtual machine configuration and those resulting from hot-spots created by uneven distribution of load across vSphere/ESX servers. |
|
The eG VM Monitor extends the eG Enterprise monitoring technology to virtual environments. Using a patent-pending In-N-Out MonitoringTM approach, the eG VM Monitor provides a comprehensive view of an vSphere/ESX Server, including the performance of the VM kernel, the service console and all of its virtual machines. Agent-based monitoring can be used for ESX servers, while agentless monitoring can be used for ESXi servers. When agent-based monitoring is used, eG agents only have to be installed on the vSphere/ESX server -- not on individual guests. Using vSphere/ESX server APIs, the agents provide an “outside view” of a guest VM’s performance. The relative resource usage levels of the guest VMs show where the performance hogs exist. To complement the outside view, the eG agent obtains an “inside view” that details the user activity, resource allocation and the application mix running inside the VM guest operating system. All the capabilities of agent-based monitoring are also available with the agentless monitoring option for VMware vSphere/ESX servers. The eG VM Monitor automatically baselines all the metrics it collects, so that IT administrators can be informed proactively of any deviations from the norm. No other virtualization monitoring solution offers this combination of features.
 |
Monitoring VM guests: eG agents track the performance of each guest VM relative to shared infrastructure resources (outside view) as well as the workload and application mix of the individual guest VMs (inside view). |
From a monitoring and management standpoint, the eG monitor for VMware infrastructures goes well beyond managing virtualized servers as discrete entities. End-to-end business service views show the applications and network devices that support each business service, and the inter-dependencies among them. Applications are associated with the virtual machines they run on, and each virtual machine is mapped to the physical machine upon which it is hosted.
The dependency of the virtual machines to physical machines is determined dynamically, so as to support the VMware VMotion® Live Migration technology. A patented root-cause diagnosis engine analyzes the service topology graphs and the virtual-to-physical machine mappings to pin-point where the problems areas in the infrastructure lie.
|
| |
 |
Monitoring and Reporting of vSphere/ESX servers: Using a custom vSphere/ESX Server model, the eG VM Monitor correlates performance across the host and guest VMs. Extensive pre-built reports enable rapid identification of bottlenecks and streamline capacity planning. |
 |
 |
 |
 |
| vSphere/ESX Host Monitoring |
 |
What is the CPU load on the vSphere/ESX kernel, on the console, and each of the virtual guests? |
 |
What is the free memory in the vSphere/ESX kernel and the console? |
 |
Which network interfaces are seeing the most traffic? |
 |
Which storage devices are seeing high activity? |
 |
How much free space is available on each of the disk partitions? |
 |
Are there processes on the console VM that are taking up excessive resources? |
| |
|
| Virtual Guests Monitoring |
 |
How many virtual guest machines are running? What are their IP addresses/host names and operating systems? |
 |
What portion of the vSphere/ESX Server’s CPU is used by each guest? |
 |
Are there times when a guest is not getting CPU cycles; i.e., is the ready time too high? |
 |
How much of the memory allocated is a guest actively using? |
 |
Is the balloon driver enabled for a guest, and how much memory has it freed for each guest? |
 |
Which processes on a guest are taking up high disk, CPU or memory resources? |
|
| |
|
 |
Is there excessive paging or memory thrashing in a guest? |
 |
Do all the disk partitions inside the guest operating system have adequate space? |
 |
Is there excessive queuing for disk access on any guest operating system? Which applications could be causing these accesses? |
| |
|
| Virtual Desktop Monitoring |
 |
How many desktops are powered on simultaneously on the vSphere/ESX Server? |
 |
Which users are logged on and when did each user login? |
 |
How much CPU, memory, disk and network resources is each desktop taking? |
 |
What is the typical duration of a user session? |
 |
Who has the peak usage times? |
 |
What applications are running on each desktop? |
| |
|
| VMotion Monitoring |
 |
Which vSphere/ESX Server is a virtual guest running on? |
 |
When was a guest moved from an vSphere/ESX Server? Which vSphere/ESX Server was the guest moved to? |
 |
Why was the guest migrated? What activities on the vSphere/ESX host caused the migration? |
|
|
|
 |
 |
 |
 |
 |
 |
 |
 |
| Combined external and an internal views of VMware vSphere/ESX servers |
Real-time performance views of what the VMware host sees about the guests and what the guests see internally. |
| Deep diagnostics for VMware servers |
With a few clicks, drill down to the exact processes causing a problem. |
| Automatic correlation of performance |
Analyze performance across layers of the VMware infrastructure - the VM host, between the host and the guests, and across VM guests. |
| In-depth VMware VDI monitoring |
Know which users logged in, when, what applications they accessed, what resources they used, etc. |
| Monitor virtual environments with service views - not as silos |
Correlate the performance across applications hosted in the VMware environments, discover VM dependencies, and identify performance bottlenecks. |
| Single agent licensing for VMware servers |
One agent monitors the VM kernel, console, and all the VM guests. |
| Compatible with VMware Live Migration |
Detect live migration of servers across vSphere/ESX guests, determine the efficiency of live migration. |
| Extensive Reporting |
Customizable executive and operations reports on every aspect of your vSphere/ESX servers. Identify bottlenecks in real-time, plan the capacity of your VMware server farm. |
|
 |
 |
 |
 |
|
VDI Monitoring is Not the Same as Server Virtualization Monitoring
Since virtual machines are used in both server virtualization and desktop virtualization, you are probably using or planning to use the same performance monitoring tool for both environments. However, as the table below shows, there are clear and distinct differences between server virtualization and desktop virtualization. You need a VDI performance monitoring solution that recognizes these differences.
| A server virtualization monitoring solution focuses on monitoring the virtualization platform (e.g., VMware vSphere/ ESX , Citrix XenServer, Microsoft Hyper-V, etc). |
A virtual desktop infrastructure includes several software and hardware tiers. The virtualization platform is only one of the tiers. An ideal VDI monitoring solution must monitor every layer of every tier including the connection brokers, Active Directory servers, web interfaces, storage devices, network devices, terminal servers, profile servers, etc. |
| Few VMs (<10) per physical server |
Many (30-70) VMs per physical server |
| The workload of a VM is similar over time because the application servers deployed on a VM do not change over a few hours. |
The workload of a VM varies depending on the user who is logged on to the VM. Depending on the user's role in an organization, the application mix running in the VM could be very different. Hence, monitoring should be based on user activity -- not VM activity. |
| VMs remain powered on all the time as the application servers they host need to be accessible at all times. |
VMs are powered on when users log on and then powered off when users log off. |
| Monitoring is mostly from the VM perspective; e.g., which VMs are on, what resources (CPU, memory, disk, etc.) are they using. |
Monitoring must be from the user perspective. To handle support calls from users, it is imperative to know which users are logged in, which VM a specific user is assigned to, and what applications he/she is accessing and what resources the user is consuming. |
| In-depth monitoring is required for monitoring applications such as Citrix, Oracle, etc. that are running inside the VMs. Hence, it is likely that monitoring agents are deployed in the VMs to monitor the applications running in the VMs and a view of the performance inside the VMs is available from these agents. |
Virtual desktops do not have server applications running in them. Hence, in-depth monitoring of applications on the desktop is not required. Furthermore, the higher number of VMs on each physical server, the higher the cost of installation, licensing and maintenance of the agents. The resource overhead resulting from agents on every desktop is also high. Therefore, from a monitoring perspective, the challenge is to monitor activities inside a VM without relying on agents to be installed in the VMs. |
VDI Monitoring Needs
Therefore, an ideal monitoring solution for virtual desktop infrastructures must:
 |
Monitor user activity, not just VM activity. Avoid requiring agents inside each virtual desktop for monitoring the desktop operating system. |
 |
Monitor the virtual desktop infrastructure end-to-end as a single business service, not as individual tiers or silos. |
 |
Be scalable to handle 50-100 virtual desktops per physical server. |
 |
Provide web-based reports on user activity. |
 |
Support a VDI-friendly licensing policy, so the monitoring system is licensed by physical servers monitored, not by server cores, CPUs, or virtual desktops. |
|
|
|
|