geneos vmware monitoring plug-in user guide v1.0 · 2018. 5. 10. · netprobe...

VMMonitoring Plug-in TechnicalReference

Functional Area: VM Monitoring Plug-in

Geneos Release: v4.6

Document Version: v1.0.0

Date Published: 16 March 2018

Copyright 2018. ITRSGroup Ltd. All rights reserved.

Information in this document is subject to change without notice. The software described in this document is furnished under a license agreement

or nondisclosure agreement. The softwaremaybe used or copied only in accordance with the termsof those agreements. No part of this

publicationmaybe reproduced, stored in a retrieval system, or transmitted in any form or anymeanselectronic or mechanical, including

photocopying and recording for anypurpose other than the purchaser's personal use without the written permission of ITRSGroup Ltd.

ITRSGroup Ltd

6th Floor, The Bonhill Building, 15 Bonhill Street,

London, EC2A4DN, UK

t: +44 (0)20 7638 6700

f: +44 (0)20 7256 5760

VMWare Monitoring Plug-in

IntroductionVMWare delivers the world’s most trusted virtualisation and cloud infrastructure solutions that accelerateIT transformation by reducing complexity and enablingmore flexible, agile service delivery.

While virtualisation has tremendous benefits, it adds new complexity when it comes tomanaging yournetwork. Virtual Machines (VMs) and their host machines need performance and availability monitoring,just like their physical server counterparts. TheGeneos VMWare plug-in monitors the VMWare ESXiserver by querying webservice API. By collecting key parameters from the VMWare host, Geneos usersare able to correlate both the host and guest health with the rich application data they collect.

Application Support teams need to have visibility of the health, performance and availability of their VirtualMachines (VMs) in order to be proactive and provide the best service to the business. Whenmultiplelayered operating systems are supporting their applications, it is just as critical to collect and analyzethosemetrics from guest and host to ensure the best possible performance to an end user.

The VMWareMonitoring plug-in provides Application Support teams with a view of the entire VMWareenvironment, drill down details to identify root cause and out of the box alerts to take actions, and fixproblems on time all within Geneos solution.

TechnologyGeneos VMWare plug-in is a Java process that uses the VMWare vSphere API to continuously monitor aVMWare host and associated virtual machines, delivering the real-timemonitoring into the Geneosframework using the XML–RPC interface.

GeneosRelease v4.6 VMMonitoring Plug-in v1.0.0 - TechnicalReference Published Date 16/03/2018

of 29

ArchitectureThe VMWare plug-in integrates with your existing architecture. You can connect the plug-in to existinggateways to allow you to correlate VMWaremonitoring information with monitoring from the applicationlevel that runs on this virtual infrastructure.

PrerequisitesThe following are required to set up the VMWareMonitoring Solution:

l Geneos XML-RPC API token

l Java 1.6+

l VMWare Solution package with dependent libs (these are included in the lib subdirectory)

l VMWare plug-in licence: VMWareMonitor.lic


of 29

Installation

SamplerSet up a sampler. This is set up as an API plug-in.

1. Set the name to “Cluster”. If you wish to change the name, make sure that this value isused in the VMWareMonitor.properties file.

2. Set the plugin type to API.

<sampler name="Cluster"><plugin><api></api></plugin></sampler>


of 29

NetprobeSelect a netprobe, preferably on themachine where you will be running the plug-in code.

Managed EntitySet up amanaged entity that joins the probe and the sampler.

1. Set the name to “VMWare”. If you wish to change the name, make sure that this value isused in the VMWareMonitor.properties file.

2. Set Options to probe, and select the probe you set up in Netprobe.

3. Reference the sampler you set up in Sampler.

<managedEntity name="VMWare"><probe ref="VMWare probe"></probe><sampler ref="Cluster"></sampler></managedEntity>

VMWare PermissionsUsing the vSphere client, ensure that the user has full administration permissions.

VMWare Solution with Dependent LibsCreate a directory on the server where you are running the netprobe you want to use tomonitor VMWare.Copy the contents of the tar file to this location.

VMWareMonitor/VMWareMonitor.jarlib/log4j-1.2.16.jarvim25.jarws-commons-util-1.0.2.jarxmlrpc-client-3.1.3.jarxmlrpc-common-3.1.3.jarxmlrpc-server-3.1.3.ja


of 29

Plug-in ConfigurationBy default, the plug-in uses a config file called VMWareMonitor.properties. You can specify a differentconfig file on the command line or use Java properties on the command line to override properties in theconfig file. If there is no config file to be found, running the plug-in the first time will generate a defaultconfig file. Confirm that the VMwareMonitor.properties file has the correct settings especially:

netprobeServer=localhostnetprobePort=7036

vSphere Connection DetailsYouwill need to supply the URL of the webservice, which is usually https://<IPADDRESSOFSERVER>/sdk,and the username and password. If you want to connect to several hosts, then supply the different URLsas a comma delimited list. By default, the plug-in will use the username and password to connect to all thehosts. You can override this by supplying a separate entry with a numeric suffix.

For example, if you want to connect to three separate servers (192.168.31.129, 192.168.31.138,192.168.31.130) using one set of credentials to log in to the first two servers and then a different set ofcredentials to log in to the third server, you would use this config:

url=https://192.168.31.129/sdk,https://192.168.31.138/sdk,https://192.168.31.130/sdkusername=Geneospassword=Tester123username3=AnotherGeneospassword3=AnotherTester

Logging ConfigurationThe logging is configured using log4j. By default, it is configured to log to the console and a log file(VMwareMonitor.log) that will roll twice a day (AM and PM).

InitialisationTo run the VMWareMonitor.jar file:

java -jar VMwareMonitor.jar


of 29

Upgrade InstructionsYou can unpack the tallball directly over an existing installation in which a new default.properties file will becreated, but the plug-in will continue to use your existing config file. Youmay need to restart your netprobeand reset your gateway connection to clear out any obsolete views or columns.

Views

GroupsThe VMWare plug-in displays a number of groups showing an overview of the virtual machines and theirassociated hosts. Each webservice is given its own group with information about the virtual machinesmanaged by that webservice. At the bottom, there is a separate VMWareMonitor group that displaysperformance information about the Hosts.

In each of the groups, there are two basic types of dataviews:

l Info View - views based onManaged objects (e.g., VirtualMachine, HostSystem). This is summaryor status information, and consequently, you would set the refresh rate to a longer interval (60seconds - 10minutes).

l Monitor View - views based on Performance counters. The real-time sampling period is 20seconds, and consequently, you would set the refresh rate to a longer interval (60 seconds - 10minutes).


of 29

Virtual Machine ViewsFor each webservice that the plug-in connects, there will be a set of Virtual Machine dataviews.

VM InfoThis view shows an overview of the VMs.

Note: The fields in boldmight not be given a value by all VM servers.

Name Description

Boot Time The timestamp when the virtual machine was most recently powered on.

This property is updated when the virtual machine is powered on from the poweredOff

state, and is cleared when the virtual machine is powered off. This property is not

updated when a virtual machine is resumed from a suspended state.

Connection State Indicates whether or not the virtual machine is available for management.

dasVmProtection The vSphere HA protection state for a virtual machine. Property is unset if vSphere

HA is not enabled.

Since vSphere API 5.0

faultToleranceState The fault tolerance state of the virtual machine.


host The host that is responsible for running a virtual machine. This property is null if thevirtual machine is not running and is not assigned to run on a particular host.


of 29

Name Description

guestMemoryUsage Guest memory utilization statistics, in MB. This is also known as active guest memory.The number can be between 0 and the configured memory size of the virtualmachine. Valid while the virtual machine is running.

hostMemoryUsage Host memory utilization statistics, in MB. This is also known as consumed hostmemory. This is between 0 and the configured resource limit. Valid while the virtualmachine is running. This includes the overhead memory of the VM.

overallCpuDemand Basic CPU performance statistics, in MHz. Valid while the virtual machine is running.


overallCpuUsage Basic CPU performance statistics, in MHz. Valid while the virtual machine is running.

powerState The current power state of the virtual machine.

question The current question, if any, that is blocking the virtual machine’s execution.

recordReplayState Record / replay state of this virtual machine.


suspendInterval The total time the virtual machine has been suspended since it was initially poweredon. This time excludes the current period, if the virtual machine is currentlysuspended. This property is updated when the virtual machine resumes, and is resetto zero when the virtual machine is powered off.

suspendTime The timestamp when the virtual machine was most recently suspended. This propertyis updated every time the virtual machine is suspended.

toolsInstallerMounted Flag to indicate whether or not the VMWare Tools installer is mounted as a CD-ROM.


of 29

Disk MonitorThis view shows the performance stats for the disk on each running VM.

Name Description

Name Name of the VM.

usage Aggregated disk I/O rate. For hosts, this metric includes the rates for all virtual machines runningon the host during the collection interval.

Read rate Average number of kilobytes read from the disk each second during the collection interval.

l VM - Rate at which data is read from each virtual disk on the virtual machine.

l Host - Rate at which data is read from each LUN on the host.

read rate = # blocksRead per second x blockSize.

Write rate Rate at which data is written to each virtual disk on the virtual machine.

write rate = # blocksRead per second x blockSize

Commandsissued

Number of SCSI commands issued during the collection interval.

CommandsAborted

Number of SCSI commands aborted during the collection interval.

Bus Resets Number of SCSI-bus reset commands issued during the collection interval.

physicaldeviceReadLatency

Average amount of time, in milliseconds, to complete read from the physical device.


of 29

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.HistoricalInterval.html





Name Description

KernelReadLatency

Average amount of time, in milliseconds, spent by VMKernel processing each SCSI readcommand.



KernelWriteLatency

Average amount of time, in milliseconds, spent by VMKernel processing each SCSI writecommand.

WriteLatency

Average amount of time taken during the collection interval to process a SCSI write commandissued by the Guest OS to the virtual machine. The sum of kernelWriteLatency anddeviceWriteLatency.

QueueWriteLatency

Average amount time taken during the collection interval per SCSI write command in theVMKernel queue.

HighestLatency

Highest latency value across all disks used by the host. Latency measures the time taken toprocess a SCSI command issued by the guest OS to the virtual machine. The kernel latency isthe time VMkernel takes to process an IO request. The device latency is the time it takes thehardware to handle the request.

AverageReadrequest persecond

Number of disk reads during the collection interval.

l VM - Number of times data was read from each virtual disk on the virtual machine.

l Host - Number of times data was read from each LUN on the host.

AverageWriterequest persecond

Number of disk writes during the collection interval.

l VM - Number of times data was written to each virtual disk on the virtual machine.

l Host - Number of times data was written to each LUN on the host.


of 29





Memory MonitorThis view shows the performance stats for thememory on the running VMs and in the admin group, thesame information is displayed for the underlying hosts.

Name Description

Name Inventory path to Guest machine (e.g., Datacenter1/vm/myvm).

Usage Amount of machine memory or “physical” memory, as follows:

Virtual machine - Guest “physical” memory that is mapped to machine memory. Includes shared

memory amount. Does not include overhead.

active Amount of memory that is actively used, as estimated by VMkernel based on recently touched

memory pages.Virtual machine - Amount of guest “physical” memory actively used.

shared Amount of guest “physical” memory shared with other virtual machines (through the VMkernel’stransparent page-sharing mechanism, a RAM de-duplication technique). Includes amount ofzero memory area.

consumed Virtual machine: Amount of guest physical memory consumed by the virtual machine for guestmemory. Consumed memory does not include overhead memory. It includes shared memoryand memory that might be reserved, but not actually used. Use this metric for charge-backpurposes.

Sharedcommon

Amount of machine memory that is shared by all powered-on virtual machines and vSphere

services on the host. Subtract this metric from the shared metric to gauge how much machine

memory is saved due to sharing:

shared - sharedcommon = machine memory (host memory) savings (KB)


of 29

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/memory_counters.html#shared

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/memory_counters.html#overhead

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/memory_counters.html#zero

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/memory_counters.html#overhead


Name Description

Swappedused

Current amount of guest physical memory swapped out to the virtual machine’s swap file by the

VMkernel. Swapped memory stays on disk until the virtual machine needs it. This statistic refers

to VMkernel swapping and not to guest OS swapping.

swapped = swapin + swapout

heap VMkernel virtual address space dedicated to VMkernel main heap and related data.

Note: For informational purposes only, not useful for performance monitoring.

Heap free Free address space in the VMkernel’s main heap. Varies based on number of physical devices

and configuration options. There is no direct way for the user to increase or decrease this

statistic.

Note: For informational purposes only, not useful for performance monitoring.

state Amount of free machine memory on the host. VMkernel has four free-memory thresholds that

affect memory reclamation:

l 0 (high) Free memory >= 6% of machine memory minus Service Console memory.

l 1 (soft) 4%

l 2 (hard) 2%

l 3 (low) 1%

l 0 (high) and 1 (soft): Swapping is favored over ballooning.

l 2 (hard) and 3 (low): Ballooning is favored over swapping.

overhead Amount of machine memory used by the VMkernel to run the virtual machine.

Swaptarget

Amount of memory available for swapping. Target size for virtual machine swap file, as

calculated by the VMkernel. The VMkernel uses values for this metric with the swap metric to

stop and start swapping, as follows:

l If swaptarget > swapped, the VMkernel can start swapping when necessary.

l If swaptarget < swapped, the VMkernel stops swapping memory.

Since swapped memory stays swapped until the virtual machine accesses it, swapped memory

can be greater than the memory swap target, possibly for a prolonged period of time. This simply

means that the swapped memory is not currently needed by the virtual machine and is not a

cause for concern.

Swap in Total amount of data that has been read into machine memory from the swap file since the virtualmachine was powered on.

Swap out Total amount of data that the VMkernel has written to the virtual machine’s swap file frommachine memory. This statistic refers to VMkernel swapping and not to guest OS swapping.


of 29

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/memory_counters.html#swapin

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/memory_counters.html#swapout

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/memory_counters.html#swapped



Name Description

Swap inRate

Rate at which memory is swapped from disk into active memory during the interval. This counterapplies to virtual machines and is generally more useful than the swapin counter to determine ifthe virtual machine is running slow due to swapping, especially when looking at real-timestatistics.

Swap outRate

Rate at which memory is being swapped from active memory to disk during the current interval.This counter applies to virtual machines and is generally more useful than the swapout counterto determine if the virtual machine is running slow due to swapping, especially when looking atreal-time statistics.


of 29


DataStore InfoThis view shows information about the datastores on this host.


Name Description

name Name of the datastore.

type Type of file system volume, such as VMFS or NFS. See type.

uncommitted Total additional storage space, in bytes, potentially used by all virtual machineson this datastore. The server periodically updates this value. It can be explicitlyrefreshed with the RefreshDatastoreStorageInfo operation. This property is validonly if accessible is true.Since vSphere API 4.0

url The unique locator for the datastore. This property is guaranteed to be valid onlyif accessible is true.

accessible The connectivity status of this datastore. If this is set to false, meaning thedatastore is not accessible, this datastore’s capacity and freespace propertiescannot be validated. Furthermore, if this property is set to false, some of theproperties in this summary and in DatastoreInfo should not be used. Refer to thedocumentation for the property of your interest. For datastores accessed frommultiple hosts, vCenter Server reports accessible as an aggregated value of theproperties reported in MountInfo. For instance, if a datastore is accessiblethrough a subset of hosts, then the value of accessible will be reported as true byvCenter Server, and the reason for a daastore being inaccessible from a host willbe reported in inaccessibleReason.


of 29

http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.host.FileSystemVolume.html

http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.Datastore.html

http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.Datastore.Summary.html


http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.Datastore.Info.html



http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.host.MountInfo.html

Name Description

capacity Maximum capacity of this datastore, in bytes. This value is updated periodicallyby the server. It can be explicitly refreshed with the Refresh operation. Thisproperty is guaranteed to be valid only if accessible is true.

freeSpace Available space of this datastore, in bytes. The server periodically updates thisvalue. It can be explicitly refreshed with the Refresh operation. This property isguaranteed to be valid only if accessible is true.

style="font-weight:bold;">maintenanceMode

The current maintenance mode state of the datastore. The set of possible values

is described in DatastoreSummaryMaintenanceModeState.



of 29



http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.Datastore.Summary.MaintenanceModeState.html

Network MonitorThis view shows the performance stats for the virtual network interface card (vNIC) on each running VM.

Name Description

Name Name of the VM.

usage Network Usage (Average).

PacketsReceived

Number of packets received by each vNIC (virtual network interface controller) on thevirtual machine.

PacketsTransmitted

Number of packets transmitted by each vNIC on the virtual machine.

Data receivedrate

The rate at which data is received across the virtual machine’s vNIC (virtual networkinterface controller).

DataTransmitted rate

The rate at which data is transmitted across the virtual machine’s vNIC (virtual networkinterface controller). This represents the bandwidth of the network.

Receivedpacketsdropped

Number of receive packets dropped during the collection interval.

TransmittedPacketsdropped

Number of transmit packets dropped during the collection interval.


of 29

CPU MonitorThis view shows the performance stats for the CPU for the running VMs and in the admin group, the sameinformation is displayed for the underlying hosts.

Name Description

Name Name of the Guest machine.

usage CPU usage as a percentage (in units of 1/100th of a percent) during the interval.

VM - Amount of actively used virtual CPU, as a percentage of total available CPU. This is the host’s

view of the CPU usage, not the guest operating system view. It is the average CPU utilization over

all available virtual CPUs in the virtual machine. For example, if a virtual machine with one virtual

CPU is running on a host that has four physical CPUs and the CPU usage is 100%, the virtual

machine is using one physical CPU completely.

virtual CPU usage = usagemhz / (# of virtual CPUs x core frequency)

Usagemhz

CPU usage, as measured in megahertz, during the interval.

VM - Amount of actively used virtual CPU. This is the host’s view of the CPU usage, not the guest

operating system view.

wait Total CPU time spent in wait stat.

ready Percentage of time (in units of 1/100th of a percent) that the virtual machine was ready, but could notget scheduled to run on the physical CPU. CPU ready time is dependent on the number of virtualmachines on the host and their CPU loads.

used Total CPU usage.

idle Total time that the CPU spent in an idle state (meaning that a virtual machine is not runnable).


of 29


Name Description

system Amount of time spent on system processes on each virtual CPU in the virtual machine. This is thehost view of the CPU usage, not the guest operating system view.


of 29

VMWare Monitor Views

AdminThis view shows the configuration information for the plug-in and the Host versions of the dataviews.


of 29

Host Memory MonitorThis view shows the performance stats for thememory on the underlying Host.

Name Description

Name The machine name of the host.

Usage Amount of machine memory used on the host. Consumed memory includes Includes memory

used by the Service Console, the VMkernel, vSphere services, plus the total consumed metrics for

all running virtual machines.

host consumed memory = total host memory - free host memory

active Amount of memory that is actively used, as estimated by VMkernel based on recently touchedmemory pages. This is a sum of all active metrics for all powered-on virtual machines plusvSphere services (such as COS, vpxa) on the host.

shared Sum of all shared metrics for all powered-on virtual machines, plus amount for vSphere serviceson the host. The host’s shared memory may be larger than the amount of machine memory ifmemory is overcommitted (the aggregate virtual machine configured memory is much greaterthan machine memory). The value of this statistic reflects how effective transparent page sharingand memory over commitment are for saving machine memory.

Sharedcommon

Amount of machine memory that is shared by all powered-on virtual machines and vSphere

services on the host. Subtract this metric from the shared metric to gauge how much machine

memory is saved due to sharing.

shared - sharedcommon = machine memory (host memory) savings (KB)


of 29


Name Description

Swappedused

Current amount of guest physical memory swapped out to the virtual machine’s swap file by the

VMkernel. Swapped memory stays on disk until the virtual machine needs it. This statistic refers to

VMkernel swapping and not to guest OS swapping.

swapped = swapin + swapout

heap VMkernel virtual address space dedicated to VMkernel main heap and related data.

Note:For informational purposes only, not useful for performance monitoring.

state Amount of free machine memory on the host. VMkernel has four free-memory thresholds that

affect memory reclamation:

l 0 (high) Free memory >= 6% of machine memory minus Service Console memory.

l 1 (soft) 4%

l 2 (hard) 2%

l 3 (low) 1%

l 0 (high) and 1 (soft): Swapping is favored over ballooning.

l 2 (hard) and 3 (low): Ballooning is favored over swapping.

overhead Amount of machine memory used by the VMkernel to run the virtual machine.

Swaptarget

Amount of memory available for swapping. Target size for virtual machine swap file, as calculatedby the VMkernel. The VMkernel uses values for this metric with the swap metric to stop and startswapping, as follows:

l If swaptarget > swapped, the VMkernel can start swapping when necessary.

l If swaptarget < swapped, the VMkernel stops swapping memory.

Since swapped memory stays swapped until the virtual machine accesses it, swapped memorycan be greater than the memory swap target, possibly for a prolonged period of time. This simplymeans that the swapped memory is not currently needed by the virtual machine and is not acause for concern.

Swap in Total amount of data that has been read into machine memory from the swap file since the virtualmachine was powered on.

Swap out Total amount of data that the VMkernel has written to the virtual machine’s swap file from machinememory. This statistic refers to VMkernel swapping and not to guest OS swapping.

Swap inRate

Rate at which memory is swapped from disk into active memory during the interval. This counterapplies to virtual machines and is generally more useful than the swapin counter to determine ifthe virtual machine is running slow due to swapping, especially when looking at real-timestatistics.

Swap outRate

Rate at which memory is being swapped from active memory to disk during the current interval.This counter applies to virtual machines and is generally more useful than the swapout counter todetermine if the virtual machine is running slow due to swapping, especially when looking at real-time statistics.


of 29

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/memory_counters.html#swapin

https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/memory_counters.html#swapout





Host Disk MonitorThis view shows the performance stats for the disk on each running VM.

Name Description

Name Name of the Host.

usage Aggregated disk I/O rate. For hosts, this metric includes the rates for the host during thecollection interval.

Read rate Average number of kilobytes read from the disk each second during the collection interval.

Host - Rate at which data is read from each LUN on the host.

read rate = # blocksRead per second x blockSize

Write rate Rate at which data is written to each virtual disk on the virtual machine.

write rate = # blocksRead per second x blockSize

Commandsissued

Number of SCSI commands issued during the collection interval.

CommandsAborted

Number of SCSI commands aborted during the collection interval.

Bus Resets Number of SCSI-bus reset commands issued during the collection interval.




of 29






Name Description

KernelReadLatency

Average amount of time, in milliseconds, spent by VMKernel processing each SCSI readcommand.



KernelWriteLatency

Average amount of time, in milliseconds, spent by VMKernel processing each SCSI writecommand.

WriteLatency

Average amount of time taken during the collection interval to process a SCSI write commandissued by the Guest OS to the virtual machine. The sum of kernelWriteLatency anddeviceWriteLatency.

QueueWriteLatency

Average amount time taken during the collection interval per SCSI write command in theVMKernel queue.

HighestLatency

Highest latency value across all disks used by the host. Latency measures the time taken toprocess a SCSI command issued by the guest OS to the virtual machine. The kernel latency isthe time VMkernel takes to process an IO request. The device latency is the time it takes thehardware to handle the request.

AverageReadrequest persecond

Host - Number of times data was read from each LUN on the host during the collection interval.

Averagewriterequest persecond

Host - Number of times data was written to each LUN on the host during the collection interval.


of 29





Host CPU MonitorThis view shows the performance stats for the CPU for the running VMs and in the admin group, the sameinformation is displayed for the underlying hosts.

Name Description

Name Name of the Host.

usage CPU usage as a Percentage (in units of 1/100th of a percent) during the interval. Actively usedCPU of the host, as a percentage of the total available CPU. Active CPU is approximately equal tothe ratio of the used CPU to the available CPU.available CPU = # of physical CPUs x clockrate100% represents all CPUs on the host. For example, if a four-CPU host is running a virtualmachine with two CPUs, and the usage is 50%, the host is using two CPUs completely.

Usagemhz

CPU usage, as measured in megahertz, during the interval. Sum of the actively used CPU of allpowered on virtual machines on a host. The maximum possible value is the frequency of theprocessors multiplied by the number of processors. For example, if you have a host with four 2GHzCPUs running a virtual machine that is using 4000MHz, the host is using two CPUs completely.4000 / (4 x 2000) = 0.50

wait Total CPU time spent in wait stat.

ready Percentage (in units of 1/100th of a percent) of time that the virtual machine was ready, but couldnot get scheduled to run on the physical CPU. CPU ready time is dependent on the number ofvirtual machines on the host and their CPU loads.

used Total CPU usage.


of 29



Name Description

Latency Latency is a measure of 3 things:

l CPU ready - Percentage of time that the virtual machine was ready, but could not getscheduled to run on the physical CPU. CPU ready time is dependent on the number ofvirtual machines on the host and their CPU loads.

l CPU swap wait - Time the virtual machine is waiting for swap page-ins. CPU Swap Wait isincluded in CPU Wait.

l Power settings - This is configured in the BIOS of the server. For a HP server change thepower setting to “OS Control” to get the most effective balance.


of 29

Host InfoThe Host information is aggregated in the admin group, which allows multiple hosts to bemonitoredtogether.

Note: The columns defined by the first host in the list will be used for subsequent hosts. This meansthat you should not attempt to monitor a 3.5 host and 4.1 or above host using the same instance of theplug-in.


of 29


Name Description

Name Name of the Host machine.

apiType Indicates whether or not the service instance represents a standalone host. If theservice instance represents a standalone host, then the physical inventory for thatservice instance is fixed to that single host. VirtualCenter server provides additionalfeatures over single hosts. For example, VirtualCenter offers multi-hostmanagement. Examples of values are:

l “VirtualCenter” - For a VirtualCenter instance.

l “HostAgent” - For host agent on an ESX Server or VMWare Server host.

apiVersion The version of the API as a dot-separated string. For example, “1.0.0”

build Build string for the server on which this call is made. For example, x.y.z-num. Thisstring does not apply to the API.

fullName The complete product name, including the version information.

instanceUuid A globally unique identifier associated with this service instance.Since vSphere API 4.0

licenseProductName The licence product name.Since vSphere API 4.0

licenseProductVersion The licence product version.Since vSphere API 4.0

localeBuild Build number for the current session’s locale. Typically, this is a small numberreflecting a localisation change from the normal product build.

localeVersion Version of the message catalog for the current session’s locale.

osType Operating system type and architecture. Examples of values are:

l win32-x86 - For x86-based Windows systems.

l linux-x86 - For x86-based Linux systems.

l vmnix-x86 - For the x86 ESX Server microkernel.

productLineId The product ID is a unique identifier for a product line. Examples of values are:

l gsx - For the VMWare Server product.

l esx - For the ESX product.

l embeddedEsx - For the ESXi product.

l vpx - For the VirtualCenter product.

vendor Name of the vendor of this product.

version Dot-separated version string. For example, “1.2”.


of 29

geneos vmware monitoring plug-in user guide v1.0 · 2018. 5. 10. · netprobe...

Documents