Virtual Dashboard

Large virtualized environments are typically characterized by hundreds of virtual hosts, with tens of VMs configured on each host. In such environments, if a mission-critical application executing on a VM experiences a slowdown, the key challenge for the administrator is to determine what caused the slowdown - is it because the VM is under-sized? is it owing to a resource contention at the virtual host level? Is it because of other resource-hungry VMs? or is it owing to resource-intensive processes spawned by the target application itself? Also, as VM migration would be rampant in such environments, administrators are required to know when, why, and to which virtual host a VM was migrated, and even assess the impact of such a shift on the source and the destination hosts.

eG Enterprise provides dedicated monitoring models for a variety of virtualization platforms to enable administrators to address the performance concerns cited above. By analyzing the resource usage of VMs from inside and outside, and using an intelligent correlation engine to differentiate problem symptoms from sources, these models accurately point to the root-cause of slowdowns experienced by a virtual application. In addition, these models are also capable of tracking the movement of VMs from one host to another and alerting administrators to the same. However, the key limitation of these models is that the aforesaid capabilities are 'hidden' inside the layers, tests, and measures offered by the models. To bring these capabilities to light, administrators would have to invest a considerable amount of time and mouse clicks!

A quicker, 'single glance' alternative to this is the Virtual Dashboard. The Virtual Dashboard provides administrators of virtualized environments the wherewithal to accurately diagnose the cause for slowdowns experienced by a virtual application, with minimal effort and time! This dashboard collates critical resource usage data from the host operating system and from 'inside' and 'outside' all the VMs on a virtual server, presents them in graphical and tabulated formats in a single interface in the eG monitoring console, and thus aids instant and effective performance analysis. In the event of a problem situation therefore, administrators can use the Virtual Dashboard to rapidly find answers to the following questions:

• Is the host experiencing a resource crunch? If so, which resource is being drained - CPU/memory/disk? Which processes executing on the host could be causing the resource bottleneck?

• How are the VMs using the physical resources of the host? Is any VM consuming resources excessively? If so, which VM is it?

• Were sufficient resources allocated to the VMs? How are the VMs using the resources allocated to them?

• Are resource-intensive processes executing on any VM? If so, which VM is being impacted, and what are the rogue processes?

• Did any VM migrate during the last hour (by default)? If so, which VM is it? Which server was it migrated to? How is the VM handling the physical and allocated resources in the destination host?

In addition to current problems, the dashboard also sheds light on the probable causes for issues that occurred in the past, thus paving the way for effective post-mortem analysis.

To view the virtual dashboard, click on the Virtual tab page that is available for a target virtual server.

The Virtual Dashboard groups the data collected into subsystems, and presents the data in the interface based on your choice of subsystem. The subsystems supported by this interface are as follows:

• Physical Server Analysis

• Outside view of VMs

• Inside view of VMs

The sections that will follow discuss each of these subsystems in detail.

Physical Server Analysis - CPU

By default, the Virtual Dashboard allows you to focus on how the host operating system and the VMs are utilizing the physical CPU resources of the target host. Accordingly, Physical Server Analysis is chosen as the Subsystem, and CPU is chosen from the View list, by default. The contents of this default CPU dashboard have been discussed below:

1. The CPU dashboard begins with dial charts that will frequently update you with the current state and values for critical CPU usage metrics related to the host operating system. You can promptly detect sudden spikes in CPU usage by the host using these dial charts.

Note:

You can configure what CPU usage statistics need to be represented using dial charts by following the steps discussed below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [CPUAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}_GAUGE

This parameter is typically set to a comma-separated list of measures for which dial charts are to be displayed in the dashboard.

By default, this parameter is set to a pre-configured list of CPU-related metrics extracted from the corresponding {InternalComponentType}.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType}_GAUGE parameter:

{InternalTest}:{InternalMeasure}:{DisplayName}

For instance, to add a dial chart for the Physical CPU Usage measure reported by the CPU - ESX test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server_GAUGE=. . . . . . .,EsxCpuSummaryTest:Usage:Physical server CPU usage

• Finally, save the file.

Note that dial charts can be used to represent only those measures that report values in percentage.

2. Clicking on a dial chart will lead you to the Layer tab page, where you can view the layer and test that reported the measure represented by that dial chart.
3. Below the dial charts, you will find a default collection of comparison bar charts that typically compare CPU usage across the host's processors, the host's subsystems, the physical CPU usage across VMs, and the virtual CPU usage across VMs. Using these graphs, resource-intensive processors, subsystems, and VMs can be accurately identified.

Note:

You can configure what CPU usage statistics need to be represented using the comparison bar charts, by following the steps discussed below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [CPUAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}

This parameter is typically set to a comma-separated list of measures for which comparison bar charts are to be displayed in the dashboard.

By default, this parameter is set to a pre-configured list of CPU-related metrics extracted from the corresponding {InternalComponentType}.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType} parameter:

{InternalTest}:{InternalMeasure}:{DisplayName}

For instance, to add a comparison graph for the VM CPU Extra measure reported by the EsxGuestDetails test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server =. . . . . . .,EsxGuestTest:Cpu_extra:VM CPU Extra

• Finally, save the file.

It is recommended that you configure comparison graphs for only those measures that support descriptors.

4. If a comparison graph appears too cluttered, you can view that graph more clearly by enlarging it. To do so, click on that graph. The graph will then appear.
5. By default, in the enlarged mode, the comparison bar chart will display all the compared elements (i.e., descriptors). This is why, the Show list is set to ALL by default. If you want the graph to display only a few best or a few worst players in a particular area, then, pick a TOP-N or LAST-N option from the Show list. Also, you can actually configure the graph to compare the performance of descriptors during a specified time period in the past so that, a past problem can be investigated, and the root-cause of the problem ascertained. For this purpose, click on the Compare History link, and then provide a past timeline.
6. To collapse the enlarged graph, click on it again.
7. Back in the dashboard, you will find that a Details of VMs table follows the comparison bar charts. By default, this table compares the physical and virtual CPU usage of each of the VMs so that, you can clearly identify the following:
• The VM causing a severe dent in the physical resources of the host;
• The VM using the allocated CPU resources excessively

By default, this table is sorted in the descending order of the Physical CPU utilization column. To sort the table in the ascending order of the same column, click on the down arrow button that appears adjacent to the column heading, Physical CPU utilization (%). To sort the table on the basis of the values of another column, click on the title of the corresponding column.

Note:

You can configure additional measure columns to the Details of VMs table by following the procedure discussed below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [CPUAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}_DATA

This parameter is typically set to a comma-separated list of measures that will appear as columns in the Details of VMs table.

By default, this parameter is set to a pre-configured list of CPU usage statistics extracted from each VM on the corresponding {InternalComponentType}.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType}_DATA parameter:

{InternalTest}:{InternalMeasure}

For instance, to add a column for the VM CPU Extra measure reported by the EsxGuestDetails test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server_DATA =. . . . . . .,EsxGuestTest:Cpu_extra

• Finally, save the file.
8. To historically analyze the physical CPU usage of the host and the VMs, you can view historical measure graphs in your dashboard, instead of the default comparison bar charts. To do this, click on the icon at the right, top corner of your dashboard. This will result in the display of measure graphs, plotted for a default duration of 1 hour, for each of the measures for which comparison bar charts were originally displayed.
9. In the event of a contention for CPU resources, you can use these measure graphs to understand how CPU usage has varied during the last hour, and when the CPU contention actually began.
10. To view a measure graph more clearly, click on it. This will enlarge the graph.
11. In the enlarged mode, you can change the Timeline of the graph and its dimension (3D or 2D). You can also pick a TOP-N or LAST-N option from the Show list to analyze the time-of-day variations in the performance of a few best/worst players in the chosen performance arena. To return to the dashboard, click on the enlarged graph.

Physical Server Analysis - Memory

To quickly analyze physical memory usage by the virtual host and its VMs, and to precisely point to the VMs that are eroding the memory resources of the host, select Memory from the View list.

The contents of The Physical Server Memory Analysis dashboard have been detailed below:

1. A glance at the pie chart in the Memory dashboard will indicate to you whether a memory crunch exists on the host or not.

Note:

By default, the pie chart will denote the size of Free memory and Used Memory on the target virtual host. If you want the pie chart to represent more measures, do the following:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [MemoryAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}_PIE

This parameter is typically set to a comma-separated list of measures that will be represented in the pie chart in the Memory dashboard.

By default, this parameter is set to the Free memory and Used memory measures.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType}_PIE parameter:

{InternalTest}:{InternalMeasure}:{DisplayName}

For instance, to make sure that the pie chart also represents the value of the Memory granted measure reported by the Memory - ESX test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server_PIE=. . . . . . .,EsxMemoryTest:Memory_granted:Memory granted

2. The dial charts in the dashboard indicate the current state and values for critical memory usage metrics related to the host operating system. You can promptly detect sudden spikes in host's memory usage using these dial charts.

Note:

You can configure what memory usage statistics need to be represented using dial charts by following the steps discussed below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [MemoryAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}_GAUGE

This parameter is typically set to a comma-separated list of measures for which dial charts are to be displayed in the dashboard.

By default, this parameter is set to a pre-configured list of memory usage-related metrics extracted from the corresponding {InternalComponentType}.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType}_GAUGE parameter:

{InternalTest}:{InternalMeasure}:{DisplayName}

For instance, to add a dial chart for the Balloon memory measure reported by the Memory - ESX test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server_GAUGE=. . . . . . .,EsxMemoryTest:Balloon_memory:Balloon memory

• Finally, save the file.

Note that dial charts can be used to represent only those measures that report values in percentage.

3. Clicking on a dial chart will lead you to the Layer tab page, where you can view the layer and test that reported the measure represented by that dial chart.
4. Below the dial charts, you will find a table that indicates the current state and the current values for a default collection of critical memory usage-related metrics. This table allows you to focus on important usage metrics so that, you can instantly detect any change in the state of any such a metric, and immediately initial remedial steps.

Note:

If need be, you can alter the list of metrics that are displayed in this table by following the steps below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [MemoryAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}_Memory_DATA

This parameter is typically set to a comma-separated list of measures that need to be included in the table of metrics in the Memory dashboard.

By default, this parameter is set to a pre-configured list of memory usage-related metrics extracted from the corresponding {InternalComponentType}.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType}_Memory_DATA parameter:

{InternalTest}:{InternalMeasure}

For instance, to add the Free physical memory measure reported by the Memory - ESX test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server_Memory_DATA =. . . . . . .,EsxMemoryTest:Machine_free_memory

• Finally, save the file.
5. Next to the table, you will find a default collection of comparison bar charts that typically compare physical memory usage across VMs. Using these graphs, memory-intensive VMs can be isolated.

Note:

You can configure what memory usage statistics need to be represented using the comparison bar charts, by following the steps discussed below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [MemoryAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}

This parameter is typically set to a comma-separated list of measures for which comparison bar charts are to be displayed in the dashboard.

By default, this parameter is set to a pre-configured list of memory usage-related metrics extracted from the corresponding {InternalComponentType}.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType} parameter:

{InternalTest}:{InternalMeasure}:{DisplayName}

For instance, to add a comparison graph for the Current swap memory measure reported by the EsxGuestDetails test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server =. . . . . . .,EsxGuestTest:Swapped_memory:Swap memory

• Finally, save the file.

It is recommended that you configure comparison graphs for only those measures that support descriptors.

6. If a comparison graph appears too cluttered, you can view that graph more clearly by enlarging it. To do so, click on that graph. The graph will then appear as depicted below:
7. By default, in the enlarged mode, the comparison bar chart will display all the compared elements (i.e., descriptors). This is why, the Show list is set to ALL by default. If you want the graph to display only a few best or a few worst players in a particular area, then, pick a TOP-N or LAST-N option from the Show list. Also, you can actually configure the graph to compare the performance of descriptors during a specified time period in the past so that, a past problem can be investigated, and the root-cause of the problem ascertained. For this purpose, click on the Compare History link, and then provide a past timeline.
8. To collapse the enlarged graph, click on it again.
9. Back in the dashboard, you will find that a Details of VMs table follows the comparison bar charts. By default, this table compares the physical and virtual memory usage of each of the VMs so that, you can clearly identify the following:
• The VM causing a severe dent in the physical memory resources of the host;
• The VM using the allocated memory resources excessively

By default, this table is sorted in thedescending order of the Physical memory consumed column. To sort the table in the ascending order of the same column, click on the down arrow button that appears adjacent to the column heading, Physical memory consumed (GB). To sort the table on the basis of the values of another column, click on the title of the corresponding column.

Note:

You can configure additional measure columns for the Details of VMs table by following the procedure discussed below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [MemoryAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}_DATA

This parameter is typically set to a comma-separated list of measures that will appear as columns in the Details of VMs table.

By default, this parameter is set to a pre-configured list of memory usage statistics extracted from each VM on the corresponding {InternalComponentType}.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType}_DATA parameter:

{InternalTest}:{InternalMeasure}

For instance, to add a column for the Current swap memory measure reported by the EsxGuestDetails test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server_DATA =. . . . . . .,EsxGuestTest:Swapped_memory

• Finally, save the file.
10. To historically analyze the physical memory usage of the host and the VMs, you can view historical measure graphs in your dashboard, instead of the default comparison bar charts. To do this, click on the icon at the right, top corner of your dashboard. This will result in the display of measure graphs, plotted for a default duration of 1 hour, for each of the measures for which comparison bar charts were originally displayed.
11. In the event of a contention for memory resources, you can use these measure graphs to understand how memory was used during the last hour, and when the memory erosion actually began.
12. To view a measure graph more clearly, click on it. This will enlarge the graph.
13. In the enlarged mode, you can change the Timeline of the graph and its dimension (3D or 2D). You can also pick a TOP-N or LAST-N option from the Show list to analyze the time-of-day variations in the performance of a few best/worst players in the chosen performance arena. To return to the dashboard, click on the enlarged graph.

The Physical Server Analysis - Disk

To quickly analyze disk activity and disk space usage by the virtual host and its VMs, and to precisely point to the VMs that are consuming too much disk space, select Disk from the View list.

The contents of The Physical Server Memory Analysis dashboard have been detailed below:

14. A glance at the pie chart in the Disk dashboard will indicate to you whether a space crunch exists on the host or not.

Note:

By default, the pie chart will denote the Free space and Used space on the target virtual host. If you want the pie chart to represent more measures, do the following:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [DiskAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}_PIE

This parameter is typically set to a comma-separated list of measures that will be represented in the pie chart in the Disk dashboard.

By default, this parameter is set to the Free space and Used space measures.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType}_PIE parameter:

{InternalTest}:{InternalMeasure}:{DisplayName}

For instance, to make sure that the pie chart also represents the value of the Physical disk capacity measure reported by the Datastores - Esx test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server_PIE=. . . . . . .,EsxDiskUsageTest:Total_capacity:Physical disk capacity

15. The dial charts in the dashboard indicate the current state and values for critical space usage metrics related to the host operating system. You can promptly detect which disk partition / storage adapter on the host is currently facing a space crunch, using these dial charts.

Note:

You can configure what disk space usage statistics need to be represented using dial charts by following the steps discussed below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [DiskAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}_GAUGE

This parameter is typically set to a comma-separated list of measures for which dial charts are to be displayed in the dashboard.

By default, this parameter is set to a pre-configured list of space usage-related metrics extracted from the corresponding {InternalComponentType}.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType}_GAUGE parameter:

{InternalTest}:{InternalMeasure}:{DisplayName}

For instance, to add a dial chart for the Percent usage measure reported by the DiskSpace - Console test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server_GAUGE=. . . . . . .,CSLDiskSpaceTest:Percent usage:Percent usage

• Finally, save the file.

Note that dial charts can be used to represent only those measures that report values in percentage.

16. Clicking on a dial chart will lead you to the Layer tab page, where you can view the layer and test that reported the measure represented by that dial chart.
17. Below the dial charts, you will find a default collection of comparison bar charts that reveal how disk space is utilized by the disk partitions on the host, and how the VMs use the disk space allocated to them. Using these graphs, disk partitions and VMs that use their disk space resources excessively, can be clearly identified.

Note:

You can configure what space usage statistics need to be represented using the comparison bar charts, by following the steps discussed below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [DiskAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}

This parameter is typically set to a comma-separated list of measures for which comparison bar charts are to be displayed in the dashboard.

By default, this parameter is set to a pre-configured list of disk space usage-related metrics extracted from the corresponding {InternalComponentType}.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType} parameter:

{InternalTest}:{InternalMeasure}:{DisplayName}

For instance, to add a comparison graph for the Percent usage measure reported by the DiskSpace - Console test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server =. . . . . . .,CSLDiskSpaceTest:Percent_usage:Percent usage

• Finally, save the file.

It is recommended that you configure comparison graphs for only those measures that support descriptors.

18. If a comparison graph appears too cluttered, you can view that graph more clearly by enlarging it. To do so, click on that graph.
19. By default, in the enlarged mode, the comparison bar chart will display all the compared elements (i.e., descriptors). This is why, the Show list is set to ALL by default. If you want the graph to display only a few best or a few worst players in a particular area, then, pick a TOP-N or LAST-N option from the Show list. Also, you can actually configure the graph to compare the past performance of descriptors so that, a past problem can be investigated, and the root-cause of the problem ascertained. For this purpose, click on the Compare History link, and then provide a past timeline .
20. To collapse the enlarged graph, click on it again.
21. Back in the dashboard, you will find that a Details of VMs table follows the comparison bar charts. By default, this table compares the space usage of the VMs configured on the target host so that, you can clearly identify the VM that may soon run out of space.

By default, this table is sorted in the descending order of the Total capacity column. To sort the table in the ascending order of the same column, click on the down arrow button that appears adjacent to the column heading, Total capacity (GB). To sort the table on the basis of the values of another column, click on the title of the corresponding column.

Note:

You can configure additional measure columns for the Details of VMs table by following the procedure discussed below:

• Edit the eg_dashboard.ini file in the {EG_INSTALL_DIR}\manager\config directory.
• In the [DiskAnalysis] section of the file, you will find a parameter of the following format for each of the virtualization platforms that is being monitored by eG Enterprise:

{InternalComponentType}_DATA

This parameter is typically set to a comma-separated list of measures that will appear as columns in the Details of VMs table.

By default, this parameter is set to a pre-configured list of space usage statistics extracted from each VM on the corresponding InternalComponentType.

• You can override this default setting by adding more measures to the comma-separated list, or by removing one/more existing measures. To add another measure, append an entry of the following format to the comma-separated list that follows the {InternalComponentType}_DATA parameter:

{InternalTest}:{InternalMeasure}

For instance, to add a column for the Disk reads measure reported by the EsxGuestDetails test of the vSphere/ESX(i) component, your entry should be: VmEsx_i_server_DATA =. . . . . . .,EsxGuestTest:Reads

• Finally, save the file.
22. To historically analyze the disk space usage of the host and the VMs, you can view historical measure graphs in your dashboard, instead of the default comparison bar charts. To do this, click on the icon at the right, top corner of your dashboard. This will result in the display of measure graphs, plotted for a default duration of 1 hour, for each of the measures for which comparison bar charts were originally displayed.
23. In the event of a space crunch, you can use these measure graphs to understand how disk space was used by the host and the VMs during the last hour, and when the space erosion actually began.
24. To view a measure graph more clearly, click on it. This will enlarge the graph.
25. In the enlarged mode, you can change the Timeline of the graph and its dimension (3D or 2D). You can also pick a TOP-N or LAST-N option from the Show list to analyze the time-of-day variations in the performance of a few best/worst players in the chosen performance arena. To return to the dashboard, click on the enlarged graph.