Microsoft Hyper-V Server agent Reference · 2020. 12. 29. · IBM Tivoli Composite Application...

152
IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent Version 08.20.06.00 Reference IBM

Transcript of Microsoft Hyper-V Server agent Reference · 2020. 12. 29. · IBM Tivoli Composite Application...

  • IBM Tivoli Composite Application Manager forMicrosoft Applications: Microsoft Hyper-VServer AgentVersion 08.20.06.00

    Reference

    IBM

  • Note

    Before using this information and the product it supports, read the information in “Notices” on page133.

    This edition applies to version 08.20.06.00 of the IBM Tivoli Composite Application Manager for Microsoft Applications:Microsoft Hyper-V Server Agent and to all subsequent releases and modifications until otherwise indicated in neweditions.© Copyright International Business Machines Corporation 2008, 2020.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

  • Contents

    Chapter 1. IBM Tivoli Composite Application Manager for MicrosoftApplications: Microsoft Hyper-V Server Agent.................................................... 1

    Chapter 2. Dashboards.......................................................................................... 3Default dashboards......................................................................................................................................3Widgets for the Default dashboards............................................................................................................4Custom views.............................................................................................................................................11

    Chapter 3. Thresholds..........................................................................................13Predefined thresholds............................................................................................................................... 13Customized thresholds..............................................................................................................................21

    Chapter 4. Attributes........................................................................................... 23Data sets for the monitoring agent............................................................................................................24Attribute descriptions................................................................................................................................28

    Availability data set.............................................................................................................................. 28Director data set...................................................................................................................................30Disk data set......................................................................................................................................... 31Enterprise Hyper-V Summary data set................................................................................................33Event Log data set................................................................................................................................ 34Hyper V Dynamic Memory Balancer data set...................................................................................... 35Hyper V Dynamic Memory VM data set............................................................................................... 36Hyper V Replica VM data set................................................................................................................38Hyper V Replication Statistics data set................................................................................................39Hyper V Server Disk data set................................................................................................................41Hyper V Server Network Interface data set.........................................................................................42Hyper-V Hypervisor Logical Processor data set.................................................................................. 44Hyper-V Hypervisor Partition data set.................................................................................................46Hyper-V Hypervisor Root Partition data set........................................................................................ 48Hyper-V Hypervisor Root Virtual Processor data set.......................................................................... 49Hyper-V Hypervisor Root Virtual Processor More data set.................................................................51Hyper-V Hypervisor Virtual Processor data set...................................................................................60Hyper-V Hypervisor Virtual Processor More data set......................................................................... 63Hyper-V Legacy Network Adapter data set......................................................................................... 71Hyper-V Summary data set..................................................................................................................72Hyper-V Task Manager Detail data set................................................................................................ 73Hyper-V Task Manager Recent Time data set..................................................................................... 80Hyper-V Virtual IDE Controller data set.............................................................................................. 88Hyper-V Virtual IDE Controller Filter data set..................................................................................... 88Hyper-V Virtual IDE Controller Win2K12 data set.............................................................................. 89Hyper-V Virtual Machine Bus data set.................................................................................................90Hyper-V Virtual Machine Health Summary data set............................................................................91Hyper-V Virtual Machine Summary data set....................................................................................... 92Hyper-V Virtual Network Adapter data set..........................................................................................94Hyper-V Virtual Storage Device data set............................................................................................. 96Hyper-V Virtual Switch data set...........................................................................................................97Hyper-V Virtual Switch Port data set................................................................................................... 98Hyper-V VM Association with Virtual Network data set....................................................................100Hyper-V VM IO APIC data set............................................................................................................ 101Hyper-V VM Vid Partition data set..................................................................................................... 102

    iii

  • Hypervisor data set............................................................................................................................ 102Memory data set................................................................................................................................ 104Memory in Percentage data set......................................................................................................... 105Migration data set.............................................................................................................................. 106Performance Object Status data set..................................................................................................107Processor data set............................................................................................................................. 109Resource Metering data set...............................................................................................................111Thread Pool Status data set...............................................................................................................112Virtual Machine data set.................................................................................................................... 114Virtual Machine Details data set........................................................................................................ 117Virtual Switch data set....................................................................................................................... 122VLAN Endpoint data set..................................................................................................................... 124VM Mig WO Cluster data set...............................................................................................................125VM Modification data set................................................................................................................... 126VM Operating System data set.......................................................................................................... 127VM Storage Migration data set...........................................................................................................128

    Accessibility features........................................................................................ 131

    Notices..............................................................................................................133Trademarks..............................................................................................................................................134Terms and conditions for product documentation.................................................................................135IBM Online Privacy Statement................................................................................................................ 135

    Index................................................................................................................ 137

    iv

  • Chapter 1. IBM Tivoli Composite Application Managerfor Microsoft Applications: Microsoft Hyper-V ServerAgent

    The IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agentoffers a central point of management for your Microsoft Hyper-V Server environment or application.

    The software provides a comprehensive means for gathering the information that is required to detectproblems early and to prevent them. Information is standardized across the system. You can monitormultiple servers from a single console. By using the Microsoft Hyper-V Server agent you can easily collectand analyze Microsoft Hyper-V Server specific information.

    Installing and configuring the agent

    Install the monitoring agent on the system where the application that you want to monitor is located.

    For more information, see the following documentation in IBM Knowledge Center:

    • IBM Cloud Application Performance Management• IBM Cloud Application Performance Management, Private

    © Copyright IBM Corp. 2008, 2020 1

    http://www.ibm.com/support/knowledgecenter/SSMKFHhttp://www.ibm.com/support/knowledgecenter/SSHLNR

  • 2 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • Chapter 2. DashboardsOpen the Application Performance Dashboard in the Cloud APM console to see a status summary of allyour applications. As you drill down to dashboards for specific applications and their supportingelements, more details are available about the selected item. Use the Microsoft Hyper-V Server agentdashboards to proactively monitor your Microsoft Hyper-V Server deployment. Each dashboard pagecontains views with key performance indicators.

    When an application that includes Microsoft Hyper-V Server managed resources is selected, the navigatorand the Status Overview tab show Microsoft Hyper-V Server in the Components group:

    • Click Components to see a single Microsoft Hyper-V Server group widget that is displayed along with agroup widget for every other data source type in the application.

    • Click the Microsoft Hyper-V Server subgroup to see a group widget for each managed resource in theapplication.

    • Click inside a Microsoft Hyper-V Server group widget or click a Microsoft Hyper-V Server managedresource from the navigator Instances section to open a dashboard with KPIs from the selectedmanaged resource.

    For more information about the KPIs, click in the view or click in the dashboard banner.

    Default dashboardsMicrosoft Hyper-V Server

    The Components page provides an overall status of the Hyper-V Server instance that is beingmonitored. Click anywhere in the group widget to get detailed information about the status andperformance of Hyper-V Server instance. If the Events tab shows a warning or critical status indicator,open the tab to see the open events and status for the application.

    Microsoft Hyper-V Server DashboardUse the MS Hyper- V Server dashboard page to know the following details:

    • Historical data related to the server health and server memory usage.• Historical data related to the server disk usage. Click the Used(%) column of any particular device to

    view the historical data related to the server disk usage of that device.• Health state, Heart Beat, Enabled State, Processor Load, and VHD file path of all the virtual

    machines that are hosted on the Hyper-V Server. Click the virtual machine name in the VirtualMachines group widget to get detailed information about that particular virtual machine.

    • Status of the Hyper-V Virtual Machine Management service.

    If the Events tab shows a warning or critical status indicator, open the tab to see the open events andstatus for the application.

    Virtual MachineUse the Virtual Machine page to know the following details:

    • The details of the virtual machine that is being monitored.• The top 5 disks of the virtual machine for which the usage is high.• The top 5 processes running on the virtual machine for which the CPU usage is high.• The top 5 processes running on the virtual machine for which the memory usage is high.• Historical data related to the CPU and memory usage.

    Virtual MachineUse the Virtual Machine page to know the following details:

    • The details of the virtual machine that is being monitored.• The top 5 disks of the virtual machine for which the usage is high.

    © Copyright IBM Corp. 2008, 2020 3

  • • The top 5 processes running on the virtual machine for which the CPU usage is high.• The top 5 processes running on the virtual machine for which the memory usage is high.• Historical data related to the CPU and memory usage.

    Additional group widgetsThese pop-up group widgets are displayed after you click a group widget for more details. Some groupwidgets have links to more granular information in a popup widget, described here.

    Widgets for the Default dashboardsMicrosoft Hyper-V Server

    The Components page provides an overall status of the Hyper-V Server instance that is beingmonitored. Click anywhere in the group widget to get detailed information about the status andperformance of Hyper-V Server instance. If the Events tab shows a warning or critical status indicator,open the tab to see the open events and status for the application.The following widgets are available in this dashboard:MS Hyper-V Server

    The MS Hyper-V Server group widget provides an HTML table that summarizes the overall healthof the Hyper-V Server.

    The following KPIs for the widget are derived from the attributes as described:

    • Disk status and count (Critical): Indicates the number of disks that are in the critical state. Thisdata is derived from the Device ID attribute in the KHV HYPER V SERVER DISK data set.

    • Disk status and count (Normal): Indicates the number of disks that are in the normal state. Thisdata is derived from the Device ID attribute in the KHV HYPER V SERVER DISK data set.

    • Disk status and count (Warning): Indicates the number of disks that are in the warning state.This data is derived from the Device ID attribute in the KHV HYPER V SERVER DISK data set.

    • Memory used (%): The percentage of memory that is utilized by the Hyper-V system. This data isderived from the MemoryUtilized attribute in the KHV HYPER V SUMMARY data set.

    • Processor used (%): The percentage of the processor that is utilized by the Hyper-V system. Thisdata is derived from the SystemCPUUtilization attribute in the KHV HYPER V SUMMARY data set.

    • VM management service: The status of the application component. For processes 'UP', 'DOWN','WARNING', or 'PROCESS_DATA_NOT_AVAILABLE': 'PROCESS_DATA_NOT_AVAILABLE' isdisplayed for a process when the matching process is running but the resource use informationcannot be collected for that process. For services 'UP', 'DOWN', or 'UNKNOWN': 'UNKNOWN' isdisplayed when the service is not installed. For functionality tests: 'PASSED' or 'FAILED' isdisplayed.. This data is derived from the Status attribute in the KHV AVAILABILITY data set.

    • VM status and count (Critical): Indicates the number of virtual machines that are in the criticalstate. This data is derived from the ElementName attribute in the KHV VIRTUAL MACHINE dataset.

    • VM status and count (Normal): Indicates the number of virtual machines that are in the normalstate. This data is derived from the ElementName attribute in the KHV VIRTUAL MACHINE dataset.

    • VMs with high load: Indicates the number of virtual machines for which the virtual processorload is high.

    Microsoft Hyper-V Server DashboardUse the MS Hyper- V Server dashboard page to know the following details:

    • Historical data related to the server health and server memory usage.• Historical data related to the server disk usage. Click the Used(%) column of any particular device to

    view the historical data related to the server disk usage of that device.

    4 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • • Health state, Heart Beat, Enabled State, Processor Load, and VHD file path of all the virtualmachines that are hosted on the Hyper-V Server. Click the virtual machine name in the VirtualMachines group widget to get detailed information about that particular virtual machine.

    • Status of the Hyper-V Virtual Machine Management service.

    If the Events tab shows a warning or critical status indicator, open the tab to see the open events andstatus for the application.The following widgets are available in this dashboard:Hyper-V Virtual Machine Management Service

    The Hyper-V Virtual Machine Management Service group widget provides an HTML table thatsummarizes the details of the Virtual Machine Management service.

    The following KPIs for the widget are derived from the attributes as described:

    • Service name: The name of the process, service, or functionality test. This name matches theexecutable name of the process, the service short name or the name of the process used to testthe application. This data is derived from the Name attribute in the KHV AVAILABILITY data set.

    • Status: The status of the application component. For processes 'UP', 'DOWN', 'WARNING', or'PROCESS_DATA_NOT_AVAILABLE': 'PROCESS_DATA_NOT_AVAILABLE' is displayed for aprocess when the matching process is running but the resource use information cannot becollected for that process. For services 'UP', 'DOWN', or 'UNKNOWN': 'UNKNOWN' is displayedwhen the service is not installed. For functionality tests: 'PASSED' or 'FAILED' is displayed.. Thisdata is derived from the Status attribute in the KHV AVAILABILITY data set.

    • Thread count: The number of threads currently allocated by this process. This attribute containsonly valid data for processes. This data is derived from the Thread Count attribute in the KHVAVAILABILITY data set.

    • Working set (MB): The working set size of the process in MB. This attribute contains only validdata for processes. This data is derived from the Working Set Size attribute in the KHVAVAILABILITY data set.

    Network Virtual Switch DetailsThe Network Virtual Switch Details group widget provides a table that gives details, such asSwitch ID, Switch Name and Health Status. It also provides a line chart that shows the percentageof Packets Per sec, Packets Received and Sent Per sec, Bytes Per sec, Bytes Received Per sec andBytes Sent Per sec during a specified period.

    The following KPIs for the widget are derived from the attributes as described:

    • Bytes per sec: The rate at which bytes were received and sent on the virtual switch. This data isderived from the BytesPersec attribute in the KHV VIRTUAL SWITCH data set.

    • Bytes received per sec: The rate at which bytes were received on the virtual switch. This data isderived from the BytesReceivedPersec attribute in the KHV VIRTUAL SWITCH data set.

    • Bytes sent per sec: The rate at which bytes were sent on the virtual switch. This data is derivedfrom the BytesSentPersec attribute in the KHV VIRTUAL SWITCH data set.

    • Health State: The current health of the element. This data is derived from the HealthStateattribute in the KHV VIRTUAL SWITCH data set.

    • Packets per sec: The rate at which packets were received and sent on the virtual switch. Thisdata is derived from the PacketsPersec attribute in the KHV VIRTUAL SWITCH data set.

    • Packets received per sec: The rate at which packets were received on the virtual switch. Thisdata is derived from the PacketsReceivedPersec attribute in the KHV VIRTUAL SWITCH data set.

    • Packets sent per sec: The rate at which packets were sent on the virtual switch. This data isderived from the PacketsSentPersec attribute in the KHV VIRTUAL SWITCH data set.

    • Switch ID: The unique identifier for the virtual switch. This data is derived from the Nameattribute in the KHV VIRTUAL SWITCH data set.

    • Switch Name: A common name of the virtual switch. This data is derived from the ElementNameattribute in the KHV VIRTUAL SWITCH data set.

    Chapter 2. Dashboards 5

  • • Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KHV VIRTUAL SWITCH data set.

    Server Disk DetailsThe Server Disk Details group widget provides a grid widget that shows the usage details of all thedisks of the server. Click the Used (%) column of any particular device to view the historical datarelated to the server disk usage of that device.

    The following KPIs for the widget are derived from the attributes as described:

    • Device ID: The unique identifier of the logical disk. This data is derived from the Device IDattribute in the KHV HYPER V SERVER DISK data set.

    • File System: The file system on the logical disk. This data is derived from the File Systemattribute in the KHV HYPER V SERVER DISK data set.

    • Total Space (GB): The total size of the logical disk drive, in GB. This data is derived from theTotal Size attribute in the KHV HYPER V SERVER DISK data set.

    • Used (%): The percentage of space that is used on the server.• Used Space (GB): The total amount of used space in GB on the logical disk. This data is derived

    from the Used Space attribute in the KHV HYPER V SERVER DISK data set.

    Server HealthThe Server Health group widget provides a line chart of historical data that shows the percentageof server memory, processor usage, server memory available and maximum processor utilizationduring a specified period.

    The following KPIs for the widget are derived from the attributes as described:

    • Server maximum processor utilization: The maximum processor utilization in percentage by thelogical processor. This data is derived from the MaxLogicalProcessor attribute in the KHV HYPERV SUMMARY data set.

    • Server memory available: The memory available in percentage on the Hyper-V system. This datais derived from the MemoryAvailable attribute in the KHV HYPER V SUMMARY data set.

    • Server memory used: The percentage of memory that is utilized by the Hyper-V system. Thisdata is derived from the MemoryUtilized attribute in the KHV HYPER V SUMMARY data set.

    • Server processor used: The percentage of the processor that is utilized by the Hyper-V system.This data is derived from the SystemCPUUtilization attribute in the KHV HYPER V SUMMARYdata set.

    • Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KHV HYPER V SUMMARY data set.

    Virtual MachinesThe Virtual Machines group widget provides a grid widget that gives details, such as Health State,Heart Beat, Enabled State, Processor Load, and VHD file path of all the virtual machines that arehosted on the Hyper-V Server. Click the name of the virtual machine to view the Virtual MachineDetails page.

    The following KPIs for the widget are derived from the attributes as described:

    • Enabled State: The enabled and disabled states of an element. This data is derived from theEnabledState attribute in the KHV VIRTUAL MACHINE DETAILS data set.

    • Health State: The current health of the element. This data is derived from the HealthStateattribute in the KHV VIRTUAL MACHINE DETAILS data set.

    • Heart Beat: The current heartbeat status for the virtual machine. This data is derived from theHeartBeat attribute in the KHV VIRTUAL MACHINE DETAILS data set.

    • Processor Load (%): The average processor load of the virtual machine. This data is derived fromthe AvgProcessorLoad attribute in the KHV PROCESSOR data set.

    6 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • • VHD file path: The path of the hard disk drive of the virtual machine.The interval for refreshingthe attribute is 10 minutes. This data is derived from the VHDFilePath attribute in the KHVVIRTUAL MACHINE DETAILS data set.

    • Virtual Machine Name: The name of the virtual machine. This data is derived from theElementName attribute in the KHV VIRTUAL MACHINE DETAILS data set.

    Virtual Machines Disk DetailsThe Virtual Machines Disk Details group widget provides a grid widget that gives details, such asVirtual Machine Name, System Name, Health State and Default Block Size of all the virtualmachines that are hosted on the Hyper-V Server. For more details about a Disk, such as MaximumDisk Allocated and Free Physical Disk click the disk row.

    The following KPIs for the widget are derived from the attributes as described:

    • Block Size: The default block size, in bytes, for the device. This data is derived from theDefaultBlockSize attribute in the KHV DISK data set.

    • Health State: The current health of the element. This data is derived from the HealthStateattribute in the KHV DISK data set.

    • System Name: The unique identifier for the virtual machine. This data is derived from theSystemName attribute in the KHV DISK data set.

    • Virtual Machine Name: Name of the virtual machine. This data is derived from theVirtualMachineName attribute in the KHV DISK data set.

    Virtual Machines Processor LoadThe Virtual Machines Processor Load group widget provides a table that gives details, such asInstance Name and Virtual Machine Name. It also provides a chart that gives top five processorload percentage details of all virtual machines that are hosted on the Hyper-V Server. For moredetails about a processor load, such as Hyper V Hypervisor Virtual Processor, Total Messages PerSec and Virtual Interrupts Per Sec, click the disk row.

    The following KPIs for the widget are derived from the attributes as described:

    • Instance Name: The name of the instance. This data is derived from the Name attribute in theKHV HYPER V HYPERVISOR VIRTUAL PROCESSOR data set.

    • Load percentage: The current percentage of the total processing power consumed by the virtualmachine. This data is derived from the LoadPercentage attribute in the KHV PROCESSOR dataset.

    • Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KHV PROCESSOR data set.

    • Virtual Machine Name: This is the name of the Virtual Machine. This data is derived from theVirtual Machine Name attribute in the KHV HYPER V HYPERVISOR VIRTUAL PROCESSOR dataset.

    Virtual MachineUse the Virtual Machine page to know the following details:

    • The details of the virtual machine that is being monitored.• The top 5 disks of the virtual machine for which the usage is high.• The top 5 processes running on the virtual machine for which the CPU usage is high.• The top 5 processes running on the virtual machine for which the memory usage is high.• Historical data related to the CPU and memory usage.

    The following widgets are available in this dashboard:CPU

    The CPU group widget provides a bar chart and a line chart. The bar chart shows the top 5processes that are running on the virtual machine for which the CPU usage is high. The line chartshows the percentage of CPU usage during a specified period.

    Chapter 2. Dashboards 7

  • The following KPIs for the widget are derived from the attributes as described:

    • CPU used (%): The percentage of time the CPU was busy.• Process: The command line string of the process.• Process CPU percentage: The percentage of CPU used by this process in the last sampling

    interval normalized to account for multiple online processors.Note that the attribute value isaveraged in synchronization with the situation or historical collection interval.

    • Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the CPU data set.

    Disk Utilization (%) - Top 5The Disk group widget provides a bar chart that shows the top 5 disks of the virtual machine forwhich the usage is high.

    The following KPIs for the widget are derived from the attributes as described:

    • Disk: The top 5 disks of the virtual machine for which the usage is high.• Used Percent: The amount of used space on a disk, expressed as a percentage.

    MemoryThe Memory group widget provides a bar chart and a line chart. The bar chart shows the top 5processes that are running on the virtual machine for which the memory usage is high. The linechart shows the percentage of memory usage during a specified period.

    The following KPIs for the widget are derived from the attributes as described:

    • Memory used (%): The amount of real memory used, expressed as a percentage.• Memory Utilization (MB): The size (in kilobytes) of the resident set size.• Net Memory used (%): The total physical memory used without considering the buffer memory

    and cached memory. The net memory used is expressed as a percentage.• Process: A concatenation of the process instance name and a unique ID Process number. Note

    that the ID Process numbers are reused, so they only identify a process for the lifetime of thatprocess.

    • Time: The local time at the agent when the data was collected.

    Virtual Machine DetailsThe Virtual Machine Details group widget provides an HTML table that summarizes the details ofthe virtual machine that is hosted on the Hyper-V Server.

    The following KPIs for the widget are derived from the attributes as described:

    • Idle time (%): The percentage of the physical processor idle time. This data is derived from thePercentIdleTime attribute in the KHV VIRTUAL MACHINE DETAILS data set.

    • Memory allocated (MB): The physical memory in MB that is allocated to the virtual machine. Thisdata is derived from the MemoryUsage attribute in the KHV VIRTUAL MACHINE DETAILS dataset.

    • Operating System: The operating system that is running on the virtual machine. This data isderived from the VM Operating System attribute in the KHV VIRTUAL MACHINE DETAILS dataset.

    • Up time: The amount of time since the virtual machine was last started.The format is DDHHMM,where DD indicates the number of days, HH indicates the number of hours, and MM indicatesthe number of minutes. This data is derived from the UpTimeDay attribute in the KHV VIRTUALMACHINE DETAILS data set.

    • VHD file size (GB): The capacity (in GB) of the current hard disk drive.This attribute issuperseded by the VHD FileSize V2 attribute.A negative value indicates that the VHD file doesnot exist or the VHD file path is not collected or the file path is too long.The interval forrefreshing the attribute is 10 minutes. This data is derived from the VHDFileSize attribute in theKHV VIRTUAL MACHINE DETAILS data set.

    8 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • Virtual MachineUse the Virtual Machine page to know the following details:

    • The details of the virtual machine that is being monitored.• The top 5 disks of the virtual machine for which the usage is high.• The top 5 processes running on the virtual machine for which the CPU usage is high.• The top 5 processes running on the virtual machine for which the memory usage is high.• Historical data related to the CPU and memory usage.

    The following widgets are available in this dashboard:CPU

    The CPU group widget provides a bar chart and a line chart. The bar chart shows the top 5processes that are running on the virtual machine for which the CPU usage is high. The line chartshows the percentage of CPU usage during a specified period.

    The following KPIs for the widget are derived from the attributes as described:

    • Command: A concatenation of the process instance name and a unique ID Process number.Note that the ID Process numbers are reused, so they only identify a process for the lifetime ofthat process.

    • CPU Used (%): The percentage of processor use, as an average across all processors in thesystem. Note that the attribute value is averaged in synch with the threshold or historicalcollection interval.

    • CPU used (%): The sum of the percentages of elapsed time that a processor has been busyexecuting instructions in non-idle privileged mode and executing non-idle threads, andexecuting instructions in non-idle user mode.

    • Time: The date and time the agent collects information as set on the monitored system.

    Disk Utilization(%) - Top 5The Disk group widget provides a bar chart that shows the top 5 disks of the virtual machine forwhich the usage is high.

    The following KPIs for the widget are derived from the attributes as described:

    • Disk: The top 5 disks of the virtual machine for which the usage is high.• Used Percent: The percentage of disk volume that is used.

    MemoryThe Memory group widget provides a bar chart and a line chart. The bar chart shows the top 5processes that are running on the virtual machine for which the memory usage is high. The linechart shows the percentage of memory usage during a specified period.

    The following KPIs for the widget are derived from the attributes as described:

    • Command: A concatenation of the process instance name and a unique ID Process number.Note that the ID Process numbers are reused, so they only identify a process for the lifetime ofthat process.

    • Memory used (%): The percent of bytes of real memory used.• Memory Utilization (MB): The number of bytes of virtual address space that a process uses.• Time: The date and time the agent collects information as set on the monitored system.

    Virtual Machine DetailsThe Virtual Machine Details group widget provides an HTML table that summarizes the details ofthe virtual machine that is hosted on the Hyper-V Server.

    The following KPIs for the widget are derived from the attributes as described:

    • Idle time (%): The percentage of the physical processor idle time. This data is derived from thePercentIdleTime attribute in the KHV VIRTUAL MACHINE DETAILS data set.

    Chapter 2. Dashboards 9

  • • Memory allocated (MB): The physical memory in MB that is allocated to the virtual machine. Thisdata is derived from the MemoryUsage attribute in the KHV VIRTUAL MACHINE DETAILS dataset.

    • Operating System: The operating system that is running on the virtual machine. This data isderived from the VM Operating System attribute in the KHV VIRTUAL MACHINE DETAILS dataset.

    • Up time: The amount of time since the virtual machine was last started.The format is DDHHMM,where DD indicates the number of days, HH indicates the number of hours, and MM indicatesthe number of minutes. This data is derived from the UpTimeDay attribute in the KHV VIRTUALMACHINE DETAILS data set.

    • VHD file size (GB): The capacity (in GB) of the current hard disk drive.This attribute issuperseded by the VHD FileSize V2 attribute.A negative value indicates that the VHD file doesnot exist or the VHD file path is not collected or the file path is too long.The interval forrefreshing the attribute is 10 minutes. This data is derived from the VHDFileSize attribute in theKHV VIRTUAL MACHINE DETAILS data set.

    Additional group widgetsThese pop-up group widgets are displayed after you click a group widget for more details. Some groupwidgets have links to more granular information in a popup widget, described here.The following widgets are available in this dashboard:Maximum Disk Allocated and Free Physical Disk

    The Disk Details group widget provides graphs that contain details of the disk that you select inthe Virtual Machines Disk Details group widget.

    The following KPIs for the widget are derived from the attributes as described:

    • Free physical disk: The free physical disk space available, in GB. This data is derived from theFreePhysicalDiskV2 attribute in the KHV DISK data set.

    • Maximum disk allocated: The total disk space in GB, assigned to the virtual disk for the virtualmachine.This is equal to (NumberOfBlocks*BlockSize)/1073741824. This data is derived fromthe MaxDiskAllocatedV2 attribute in the KHV DISK data set.

    • Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KHV DISK data set.

    Server Disk Percent Used (history)The Server Disk Percent Used (history) pop-up shows a line chart that shows the percentage ofserver disk usage during a specified period.

    The following KPIs for the widget are derived from the attributes as described:

    • Percent Used (%): The percentage of disk space that is used on the server.• Timestamp: The local time at the agent when the data was collected. This data is derived from

    the Timestamp attribute in the KHV HYPER V SERVER DISK data set.

    VM Processor LoadThe Processor Load Details group widget provides graphs that contain details of the processorload that you select in the Virtual Machines Processor Load Details group widget.

    The following KPIs for the widget are derived from the attributes as described:

    • Percent hypervisor run time: The percentage of time that the guest virtual processor takes to runthe hypervisor code on a logical processor. This data is derived from the Pct Hypervisor RunTime attribute in the KHV HYPER V HYPERVISOR VIRTUAL PROCESSOR data set.

    • Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KHV HYPER V HYPERVISOR VIRTUAL PROCESSOR data set.

    • Total messages per sec: The rate at which the guest code processes the total messages on thevirtual processor. This data is derived from the Total Messages Per Sec attribute in the KHVHYPER V HYPERVISOR VIRTUAL PROCESSOR data set.

    10 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • • Virtual interrupts per sec: The rate at which virtual interrupts are delivered to the virtualprocessor. This data is derived from the Virtual Interrupts Per Sec attribute in the KHV HYPER VHYPERVISOR VIRTUAL PROCESSOR data set.

    Custom viewsAfter you select an application that includes a Microsoft Hyper-V Server managed resource, the CustomViews tab is available for displaying and building custom dashboard pages with attribute values from theMicrosoft Hyper-V Server agent. You can quickly build monitoring pages for an application and save themfor viewing.

    Only a subset of Microsoft Hyper-V Server agent attributes, which are the most useful for reporting, areavailable for custom views. These attributes are shown in italic in Chapter 4, “Attributes,” on page 23.

    Chapter 2. Dashboards 11

  • 12 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • Chapter 3. ThresholdsThresholds test for certain conditions on your managed resources, such as memory usage over 95%, andraise an event when the conditions have been met. The agent comes with predefined thresholds that youcan use to monitor your Microsoft Hyper-V Server environment. You can create additional thresholds forthe areas of interest.

    After you click System Configuration > Threshold Manager, select Microsoft Hyper-V Server as thedata source type to see all the available thresholds.

    Predefined thresholdsThe thresholds are organized in the Cloud APM console Threshold Manager by the data set for which theywere written. The Microsoft Hyper-V Server agent has the following predefined thresholds:KHV_HV_Disk_Utilization_Crit

    The percentage of server disk usage is greater than or equal to 80.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SERVER_DISK.Disk_Utilization *GE 80.00

    This threshold is evaluated every 4 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the Device_ID attribute.

    This threshold uses the following attributes: Hyper_V_Server_Disk.Disk_Utilization[KHVHVSDISK.DISKUTIL], Hyper_V_Server_Disk.Device_ID [KHVHVSDISK.DEVICEID].

    KHV_HV_Disk_Utilization_WarnThe percentage of the server disk usage is 70 - 80.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SERVER_DISK.Disk_Utilization *GE 70.00 *AND *VALUEKHV_HYPER_V_SERVER_DISK.Disk_Utilization *LT 80.00

    This threshold is evaluated every 5 minutes 30 seconds.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the Device_ID attribute.

    This threshold uses the following attributes: Hyper_V_Server_Disk.Disk_Utilization[KHVHVSDISK.DISKUTIL], Hyper_V_Server_Disk.Device_ID [KHVHVSDISK.DEVICEID].

    KHV_HV_LP_ContextSwitchesLogical processor context switches are going high.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_HYPERVISOR_LOGICAL_PROCESSOR.Context_Switches_Per_Sec*GE 15000 *AND *VALUE KHV_HYPER_V_HYPERVISOR_LOGICAL_PROCESSOR.Name *NE'_Total'

    This threshold is evaluated every 10 minutes.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the NAME attribute.

    This threshold uses the following attributes:Hyper_V_Hypervisor_Logical_Processor.Context_Switches_Per_Sec [KHVHYLPROC.CONTXTSWIT]

    © Copyright IBM Corp. 2008, 2020 13

  • (not visible in the UI), Hyper_V_Hypervisor_Logical_Processor.Name [KHVHYLPROC.NAME] (notvisible in the UI).

    KHV_HV_LP_Utilization_WarnThe load on the logical processor of the Hypervisor is 70% or greater.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_HYPERVISOR_LOGICAL_PROCESSOR.Pct_Total_Run_Time *GE70.00 *AND *VALUE KHV_HYPER_V_HYPERVISOR_LOGICAL_PROCESSOR.Name *NE '_Total'

    This threshold is evaluated every 4 minutes 30 seconds.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the NAME attribute.

    This threshold uses the following attributes:Hyper_V_Hypervisor_Logical_Processor.Pct_Total_Run_Time [KHVHYLPROC.PCTTOTALRT] (notvisible in the UI), Hyper_V_Hypervisor_Logical_Processor.Name [KHVHYLPROC.NAME] (not visible inthe UI).

    KHV_HV_Memory_Utilization_CritThe percentage of memory usage of the server is greater than 95.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SUMMARY.MemoryUtilized *GE 95

    This threshold is evaluated every 4 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.MemoryUtilized[KHVHYPERV.UTILIZE].

    KHV_HV_Memory_Utilization_WarnThe percentage of memory usage of the server is 75 - 95.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SUMMARY.MemoryUtilized *GE 75 *AND *VALUEKHV_HYPER_V_SUMMARY.MemoryUtilized *LT 95

    This threshold is evaluated every 5 minutes 30 seconds.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.MemoryUtilized[KHVHYPERV.UTILIZE].

    KHV_HV_NWAdapter_FramesDroppedThe network frames are dropped.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_LEGACY_NETWORK_ADAPTER.Frames_Dropped *GT 0.0

    This threshold is evaluated every 5 minutes 30 seconds.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the NAME attribute.

    This threshold uses the following attributes: Hyper_V_Legacy_Network_Adapter.Frames_Dropped[KHVLEGNWAD.FRAMES_DRO] (not visible in the UI), Hyper_V_Legacy_Network_Adapter.Name[KHVLEGNWAD.NAME] (not visible in the UI).

    14 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • KHV_HV_PCPU_Utilization_CritThe percentage of system processor usage is greater than or equal to 90.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SUMMARY.SystemCPUUtilization *GE 90

    This threshold is evaluated every 3 minutes 30 seconds.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.SystemCPUUtilization[KHVHYPERV.SYSTEMC].

    KHV_HV_PCPU_Utilization_WarnThe percentage of system processor usage is 59 - 90.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SUMMARY.SystemCPUUtilization *GT 59 *AND *VALUEKHV_HYPER_V_SUMMARY.SystemCPUUtilization *LT 90

    This threshold is evaluated every 4 minutes 30 seconds.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.SystemCPUUtilization[KHVHYPERV.SYSTEMC].

    KHV_HV_PDisk_Latency_CritThe physical disk latency is more than or equal to 25 ms.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SUMMARY.DiskReadLatency *GE 25 *OR *VALUEKHV_HYPER_V_SUMMARY.DiskWriteLatency *GE 25

    This threshold is evaluated every 3 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.DiskReadLatency[KHVHYPERV.DISKREA] (not visible in the UI), Hyper_V_Summary.DiskWriteLatency[KHVHYPERV.DISKWRI] (not visible in the UI).

    KHV_HV_PDisk_Latency_WarnThe physical disk latency is 15 ms - 25 ms.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SUMMARY.DiskReadLatency *GT 15 *OR *VALUEKHV_HYPER_V_SUMMARY.DiskReadLatency *LT 25 *OR *VALUEKHV_HYPER_V_SUMMARY.DiskWriteLatency *GT 15 *OR *VALUEKHV_HYPER_V_SUMMARY.DiskWriteLatency *LT 25

    This threshold is evaluated every 3 minutes.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.DiskReadLatency[KHVHYPERV.DISKREA] (not visible in the UI), Hyper_V_Summary.DiskWriteLatency[KHVHYPERV.DISKWRI] (not visible in the UI).

    Chapter 3. Thresholds 15

  • KHV_HV_PDisk_Usage_CritThe physical disk utilization is high.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_EVENT_LOG.Event_ID *EQ 4096 *AND *VALUEKHV_EVENT_LOG.Event_Source *EQ 'Microsoft-Windows-Hyper-V-Integration-KvpExchange'

    This threshold is evaluated every None. Data is analyzed when it becomes available..

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the Log_Name attribute.

    This threshold uses the following attributes: Event_Log.Event_ID [KHVEVTLOG.EVTID] (not visible inthe UI), Event_Log.Event_Source [KHVEVTLOG.EVTSOURCE] (not visible in the UI),Event_Log.Log_Name [KHVEVTLOG.LOGNAME] (not visible in the UI).

    KHV_HV_PMemory_Available_CritThe available physical memory is less than 6%.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SUMMARY.MemoryAvailable *LE 5

    This threshold is evaluated every 4 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.MemoryAvailable[KHVHYPERV.AVAILAB].

    KHV_HV_PMemory_Available_WarnThe available physical memory is 5% - 10%.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SUMMARY.MemoryAvailable *LT 10 *AND *VALUEKHV_HYPER_V_SUMMARY.MemoryAvailable *GT 5

    This threshold is evaluated every 4 minutes 30 seconds.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.MemoryAvailable[KHVHYPERV.AVAILAB].

    KHV_HV_PNW_Utilization_CritThe physical network utilization is more than or equal to 65%.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_SUMMARY.NetworkUtilization *GE 65

    This threshold is evaluated every 3 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.NetworkUtilization[KHVHYPERV.NETWORK] (not visible in the UI).

    KHV_HV_PNW_Utilization_WarnThe physical network interface utilization is 40% - 65%.

    The default configuration has the following SQL syntax:

    16 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • *IF *VALUE KHV_HYPER_V_SUMMARY.NetworkUtilization *GT 40 *AND *VALUEKHV_HYPER_V_SUMMARY.NetworkUtilization *LT 65

    This threshold is evaluated every 3 minutes.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the SystemCPUUtilization attribute.

    This threshold uses the following attributes: Hyper_V_Summary.NetworkUtilization[KHVHYPERV.NETWORK] (not visible in the UI).

    KHV_HV_RVP_Utilization_CritThe root virtual processor load is more than or equal to 90%.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_HYPERVISOR_ROOT_VIRTUAL_PROCESSOR.Pct_Total_Run_Time*GE 90

    This threshold is evaluated every 3 minutes 30 seconds.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the NAME attribute.

    This threshold uses the following attributes:Hyper_V_Hypervisor_Root_Virtual_Processor.Pct_Total_Run_Time [KHVHYRPROC.TOTAL_RUN_] (notvisible in the UI), Hyper_V_Hypervisor_Root_Virtual_Processor.Name [KHVHYRPROC.NAME] (notvisible in the UI).

    KHV_HV_RVP_Utilization_WarnThe hypervisor root virtual processor load is 59% - 90%.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_HYPERVISOR_ROOT_VIRTUAL_PROCESSOR.Pct_Total_Run_Time*GE 60.00 *AND *VALUEKHV_HYPER_V_HYPERVISOR_ROOT_VIRTUAL_PROCESSOR.Pct_Total_Run_Time *LT 90.00

    This threshold is evaluated every 4 minutes 30 seconds.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the NAME attribute.

    This threshold uses the following attributes:Hyper_V_Hypervisor_Root_Virtual_Processor.Pct_Total_Run_Time [KHVHYRPROC.TOTAL_RUN_] (notvisible in the UI), Hyper_V_Hypervisor_Root_Virtual_Processor.Name [KHVHYRPROC.NAME] (notvisible in the UI).

    KHV_HV_VM_ProcessorLoad_CritThe load on the virtual machine procesor has exceeded the critical threshold.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_PROCESSOR.AvgProcessorLoad *GE 90.00

    This threshold is evaluated every 3 minutes 30 seconds.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the VirtualMachineName attribute.

    This threshold uses the following attributes: Processor.AvgProcessorLoad [KHVGETPRO0.APLOAD],Processor.VirtualMachineName [KHVGETPRO0.VIRMACNAME].

    KHV_HV_VM_Status_CritThe status of the virtual machine is critical.

    The default configuration has the following SQL syntax:

    Chapter 3. Thresholds 17

  • *IF *VALUE KHV_VIRTUAL_MACHINE.VMStatusCrit *EQ Critical

    This threshold is evaluated every 3 minutes 30 seconds.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the ElementName attribute.

    This threshold uses the following attributes: Virtual_Machine.VMStatusCrit [KHVGETVIR0.VMSTATC](not visible in the UI), Virtual_Machine.ElementName [KHVGETVIR0.ELEMENTNAM].

    KHV_HV_VP_Utilization_CritThe virtual machine processor load is more than or equal to 90%.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_HYPERVISOR_VIRTUAL_PROCESSOR.Total_Run_Time *GE 90*AND *VALUE KHV_HYPER_V_HYPERVISOR_VIRTUAL_PROCESSOR.Name *NE '_Total'

    This threshold is evaluated every 3 minutes 30 seconds.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the NAME attribute.

    This threshold uses the following attributes: Hyper_V_Hypervisor_Virtual_Processor.Total_Run_Time[KHVHYVPROC.TOTAL_RUN_] (not visible in the UI), Hyper_V_Hypervisor_Virtual_Processor.Name[KHVHYVPROC.NAME].

    KHV_HV_VP_Utilization_WarnThe virtual machine processor load is 59% - 90%.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_HYPERVISOR_VIRTUAL_PROCESSOR.Total_Run_Time *GE 60.00*AND *VALUE KHV_HYPER_V_HYPERVISOR_VIRTUAL_PROCESSOR.Total_Run_Time *LT90.00 *AND *VALUE KHV_HYPER_V_HYPERVISOR_VIRTUAL_PROCESSOR.Name *NE '_Total'

    This threshold is evaluated every 4 minutes 30 seconds.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the NAME attribute.

    This threshold uses the following attributes: Hyper_V_Hypervisor_Virtual_Processor.Total_Run_Time[KHVHYVPROC.TOTAL_RUN_] (not visible in the UI), Hyper_V_Hypervisor_Virtual_Processor.Name[KHVHYVPROC.NAME].

    KHV_HV_VStorageDevice_WarnAn error occurred on the virtual storage device.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_VIRTUAL_STORAGE_DEVICE.Error_Count *GT 0

    This threshold is evaluated every 10 minutes.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the NAME attribute.

    This threshold uses the following attributes: Hyper_V_Virtual_Storage_Device.Error_Count[KHVVSTORDV.ERRORCNT] (not visible in the UI), Hyper_V_Virtual_Storage_Device.Name[KHVVSTORDV.NAME] (not visible in the UI).

    KHV_HV_VSwitch_PacketsFloodedThe network packets are flooded.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_VIRTUAL_SWITCH.Packets_Flooded_Per_Sec *GT 0.0

    18 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • This threshold is evaluated every 15 minutes.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the NAME attribute.

    This threshold uses the following attributes: Hyper_V_Virtual_Switch.Packets_Flooded_Per_Sec[KHVVIRSWIT.PACKETS_F0] (not visible in the UI), Hyper_V_Virtual_Switch.Name[KHVVIRSWIT.NAME] (not visible in the UI).

    KHV_Image_Mgmt_Service_DownHyper-V Image Management Service is down.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_AVAILABILITY.Name *EQ vhdsvc *AND *VALUEKHV_AVAILABILITY.Status *EQ DOWN

    This threshold is evaluated every 10 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the Application_Component attribute.

    This threshold uses the following attributes: Availability.Name [KHVAVAIL.NAME], Availability.Status[KHVAVAIL.STATUS].

    KHV_Mem_On_Balancer_Node_LowAvailable memory on the balancer node is low.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_MEMORY_IN_PERCENTAGE.PercentageAvailableMemory *LE 10

    This threshold is evaluated every 5 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the PercentageAvailableMemory attribute.

    This threshold uses the following attributes: Memory_in_Percentage.PercentageAvailableMemory[KHVMEMIPER.PERAMEM] (not visible in the UI).

    KHV_Network_Service_DownHyper-V Networking Management Service is down.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_AVAILABILITY.Name *EQ nvspwmi *AND *VALUEKHV_AVAILABILITY.Status *EQ DOWN

    This threshold is evaluated every 10 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the Application_Component attribute.

    This threshold uses the following attributes: Availability.Name [KHVAVAIL.NAME], Availability.Status[KHVAVAIL.STATUS].

    KHV_VM_Disk_HealthStateHealth of the virtual disks running on virtual machines.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_DISK.HealthState *EQ Non-Functional

    This threshold is evaluated every 5 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the VirtualMachineName attribute.

    Chapter 3. Thresholds 19

  • This threshold uses the following attributes: Disk.HealthState [KHVGETDIS0.HEALTHSTAT],Disk.VirtualMachineName [KHVGETDIS0.VIRMACNAME].

    KHV_VM_Heartbeat_CritHyper-V Virtual Machine heartbeat failed.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_VIRTUAL_MACHINE.HeartBeat *EQ Error *OR *VALUEKHV_VIRTUAL_MACHINE.HeartBeat *EQ 'No_Contact' *OR *VALUEKHV_VIRTUAL_MACHINE.HeartBeat *EQ 'Lost_Communication'

    This threshold is evaluated every 3 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the ElementName attribute.

    This threshold uses the following attributes: Virtual_Machine.HeartBeat [KHVGETVIR0.HEARTBEAT],Virtual_Machine.ElementName [KHVGETVIR0.ELEMENTNAM].

    KHV_VM_Memory_HealthStateHealth of the virtual memory running on the virtual machine.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_MEMORY.HealthState *EQ Non-Functional

    This threshold is evaluated every 5 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the VirtualMachineName attribute.

    This threshold uses the following attributes: Memory.HealthState [KHVGETMEM0.HEALTHSTAT] (notvisible in the UI), Memory.VirtualMachineName [KHVGETMEM0.VIRMACNAME] (not visible in the UI).

    KHV_VM_Mgmt_Service_DownThe Hyper-V Virtual Machine Management service is down.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_AVAILABILITY.Name *EQ vmms *AND *VALUEKHV_AVAILABILITY.Status *EQ DOWN

    This threshold is evaluated every 5 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the Application_Component attribute.

    This threshold uses the following attributes: Availability.Name [KHVAVAIL.NAME], Availability.Status[KHVAVAIL.STATUS].

    KHV_VM_ProcessorLoad_CritVirtual machine processor load is more than or equal to 90%.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_PROCESSOR.LoadPercentage *GE 90

    This threshold is evaluated every 4 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the VirtualMachineName attribute.

    This threshold uses the following attributes: Processor.LoadPercentage[KHVGETPRO0.LOADPERCEN], Processor.VirtualMachineName [KHVGETPRO0.VIRMACNAME].

    KHV_VM_Processor_WarnThe virtual machine processor load is between 70% and 90%.

    20 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • The default configuration has the following SQL syntax:

    *IF *VALUE KHV_PROCESSOR.LoadPercentage *GT 70 *AND *VALUEKHV_PROCESSOR.LoadPercentage *LT 90

    This threshold is evaluated every 5 minutes.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the VirtualMachineName attribute.

    This threshold uses the following attributes: Processor.LoadPercentage[KHVGETPRO0.LOADPERCEN], Processor.VirtualMachineName [KHVGETPRO0.VIRMACNAME].

    KHV_VM_Replication_Health_CritReplication health of the virtual machine is in critical state.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_REPLICATION_STATISTICS.Replication_Health *EQCritical

    This threshold is evaluated every 4 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the Virtual_Machine_Name attribute.

    This threshold uses the following attributes: Hyper_V_Replication_Statistics.Replication_Health[KHVHYPVRST.REPHEALTH] (not visible in the UI),Hyper_V_Replication_Statistics.Virtual_Machine_Name [KHVHYPVRST.VMNAME] (not visible in theUI).

    KHV_VM_Replication_Health_WarnReplication health of the virtual machine is in warning state.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_HYPER_V_REPLICATION_STATISTICS.Replication_Health *EQ Warning

    This threshold is evaluated every 5 minutes 30 seconds.

    The severity of this threshold is Warning.

    The threshold is evaluated for each distinct value of the Virtual_Machine_Name attribute.

    This threshold uses the following attributes: Hyper_V_Replication_Statistics.Replication_Health[KHVHYPVRST.REPHEALTH] (not visible in the UI),Hyper_V_Replication_Statistics.Virtual_Machine_Name [KHVHYPVRST.VMNAME] (not visible in theUI).

    KHV_VM_Switch_HealthStateHealth of the virtual switch running on the virtual machine.

    The default configuration has the following SQL syntax:

    *IF *VALUE KHV_VIRTUAL_SWITCH.HealthState *EQ Non-Functional

    This threshold is evaluated every 5 minutes.

    The severity of this threshold is Critical.

    The threshold is evaluated for each distinct value of the ElementName attribute.

    This threshold uses the following attributes: Virtual_Switch.HealthState[KHVMSVMVI4.HEALTHSTAT], Virtual_Switch.ElementName [KHVMSVMVI4.ELENAME].

    Customized thresholdsYou can use the predefined thresholds as a starting point for event monitoring, and create your ownthresholds as conditions arise that you want to monitor.

    Chapter 3. Thresholds 21

  • The Microsoft Hyper-V Server agent has many data sets that you can use to create thresholds to monitorfor specific conditions. For descriptions of the data sets, see Chapter 4, “Attributes,” on page 23.

    Tip: The hover help for the Threshold Editor Data set field has a Learn more link to the attributedescriptions for the selected data set.

    22 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • Chapter 4. AttributesAttributes are the application properties that are being measured and reported by the IBM TivoliComposite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent. Attributesmake up the key performance indicators (KPIs) that are reported, and you can use them to createthresholds for conditions that you want to monitor.

    About attributesAttributes are organized into data sets (also referred to as attribute groups). The values can be selectivelydisplayed in dashboards or used to define a threshold.

    The most recent data sample of the attributes in the data set are used after you open a dashboard or starta threshold.Dashboards

    Only a subset of Microsoft Hyper-V Server agent attributes is displayed in the dashboards. Queries tothe dashboard data provider specify which attribute values to request from the managed resource.These attributes are shown in italic in this chapter. You can use these attributes to create the chartsand tables in custom dashboard pages.

    ThresholdsYou can define thresholds that monitor the state of your operating system, database, or applicationand open an event when the threshold is exceeded. You use attributes to define thresholds thatdescribe a condition that you want to test. After the threshold is started, the attribute values that arespecified in the threshold are compared with the values collected by the Microsoft Hyper-V Serveragent. After the condition is met, an event is registered and you are alerted by indicators in theApplication Performance Dashboard navigator, All My Applications summary boxes, and the Eventstab.

    The Microsoft Hyper-V Server agent comes with predefined thresholds that are enabled and startedwith the agent or data collector. If you edit a predefined threshold, such as to change the condition orseverity, it is no longer treated as a predefined threshold but considered a custom threshold.

    All Microsoft Hyper-V Server agent attributes, unless otherwise noted, can be used to create customthresholds. The Events tab has a table of open events with information, including threshold name,severity, source, and display item. You can expand an event row to see the formula and drill down tothe dashboard for the managed resource.

    Some attributes names display differently in the Threshold Editor, as shown in parentheses after thename, such as "Object Count (OBJECT_COUNT)".

    Historical data configurationsThe Microsoft Hyper-V Server agent collects historical data for key data sets that are shown in thedashboards. A dashboard page that includes historical views from the managed resource instance hasa time selector tool for adjusting the time range. With line charts, you can also compare the valueswith a previous day, up to the number of days that have been saved.

    Additional information about attributes

    Note the following conditions:

    • When no data can be collected for a data set, an empty result is returned (no rows of data)• When a specific attribute cannot be collected, the value 0 or "" is returned unless otherwise specified in

    a particular attribute (for example, "N/A")• Any numeric attribute value that is greater than the largest (positive or negative) number that can be

    represented by that type returns the corresponding maximum or minimum value (for example, themaximum value for a 32-bit number is 2,147,483,647). These values are displayed as text values thatare defined by the data set, such as "Value Exceeds Maximum" or "Value Exceeds Minimum".

    © Copyright IBM Corp. 2008, 2020 23

  • Numeric attributes have characteristics that are indicated in parentheses after the data type, such as"(32-bit numeric property)". A numeric attribute value can be 32-bit or 64-bit or some other size. Thevalue type can be gauge, which means it varies, like a speedometer; counter, which counts and alwaysincreases; or numeric property, such as disk size.

    For a list of the data sets, a list of the attributes in each data set, and descriptions of the attributes in theMicrosoft Hyper-V Server agent, see “Data sets for the monitoring agent” on page 24 and “Attributedescriptions” on page 28.

    Data sets for the monitoring agentThe Microsoft Hyper-V Server agent contains the following data sets.

    • Data set name: Availability

    – Table name: KHVAVAIL– Historical table name: KHV_AVAILABILITY or KHVAVAIL

    • Data set name: Director

    – Table name: KHVDIRECTO– Historical table name: KHV_DIRECTOR or KHVDIRECTO

    • Data set name: Disk

    – Table name: KHVGETDIS0– Historical table name: KHV_DISK or KHVGETDIS0

    • Data set name: Enterprise Hyper-V Summary

    – Table name: KHVVHYPERV– Historical table name: KHV_ENTERPRISE_HYPER_V_SUMMARY or KHVVHYPERV

    • Data set name: Event Log

    – Table name: KHVEVTLOG– Historical table name: KHV_EVENT_LOG or KHVEVTLOG

    • Data set name: Hyper V Dynamic Memory Balancer

    – Table name: KHVHYVDMMB– Historical table name: KHV_HYPER_V_DYNAMIC_MEMORY_BALANCER or KHVHYVDMMB

    • Data set name: Hyper V Dynamic Memory VM

    – Table name: KHVHYVDMVM– Historical table name: KHV_HYPER_V_DYNAMIC_MEMORY_VM or KHVHYVDMVM

    • Data set name: Hyper V Replica VM

    – Table name: KHVHYPERVR– Historical table name: KHV_HYPER_V_REPLICA_VM or KHVHYPERVR

    • Data set name: Hyper V Replication Statistics

    – Table name: KHVHYPVRST– Historical table name: KHV_HYPER_V_REPLICATION_STATISTICS or KHVHYPVRST

    • Data set name: Hyper V Server Disk

    – Table name: KHVHVSDISK– Historical table name: KHV_HYPER_V_SERVER_DISK or KHVHVSDISK

    • Data set name: Hyper V Server Network Interface

    – Table name: KHVHVSVNWI– Historical table name: KHV_HYPER_V_SERVER_NETWORK_INTERFACE or KHVHVSVNWI

    24 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • • Data set name: Hyper-V Hypervisor Logical Processor

    – Table name: KHVHYLPROC– Historical table name: KHV_HYPER_V_HYPERVISOR_LOGICAL_PROCESSOR or KHVHYLPROC

    • Data set name: Hyper-V Hypervisor Partition

    – Table name: KHVHYPART– Historical table name: KHV_HYPER_V_HYPERVISOR_PARTITION or KHVHYPART

    • Data set name: Hyper-V Hypervisor Root Partition

    – Table name: KHVHYRPART– Historical table name: KHV_HYPER_V_HYPERVISOR_ROOT_PARTITION or KHVHYRPART

    • Data set name: Hyper-V Hypervisor Root Virtual Processor

    – Table name: KHVHYRPROC– Historical table name: KHV_HYPER_V_HYPERVISOR_ROOT_VIRTUAL_PROCESSOR or KHVHYRPROC

    • Data set name: Hyper-V Hypervisor Root Virtual Processor More

    – Table name: KHVHYRPROM– Historical table name: KHV_HYPER_V_HYPERVISOR_ROOT_VIRTUAL_PROCESSOR_MORE or

    KHVHYRPROM• Data set name: Hyper-V Hypervisor Virtual Processor

    – Table name: KHVHYVPROC– Historical table name: KHV_HYPER_V_HYPERVISOR_VIRTUAL_PROCESSOR or KHVHYVPROC

    • Data set name: Hyper-V Hypervisor Virtual Processor More

    – Table name: KHVHYVPROM– Historical table name: KHV_HYPER_V_HYPERVISOR_VIRTUAL_PROCESSOR_MORE or

    KHVHYVPROM• Data set name: Hyper-V Legacy Network Adapter

    – Table name: KHVLEGNWAD– Historical table name: KHV_HYPER_V_LEGACY_NETWORK_ADAPTER or KHVLEGNWAD

    • Data set name: Hyper-V Summary

    – Table name: KHVHYPERV– Historical table name: KHV_HYPER_V_SUMMARY or KHVHYPERV

    • Data set name: Hyper-V Task Manager Detail

    – Table name: KHVTASKMD– Historical table name: KHV_HYPER_V_TASK_MANAGER_DETAIL or KHVTASKMD

    • Data set name: Hyper-V Task Manager Recent Time

    – Table name: KHVTASKMDR– Historical table name: KHV_HYPER_V_TASK_MANAGER_RECENT_TIME or KHVTASKMDR

    • Data set name: Hyper-V Virtual IDE Controller

    – Table name: KHVVIDECON– Historical table name: KHV_HYPER_V_VIRTUAL_IDE_CONTROLLER or KHVVIDECON

    • Data set name: Hyper-V Virtual IDE Controller Filter

    – Table name: KHVVIDECFL– Historical table name: KHV_HYPER_V_VIRTUAL_IDE_CONTROLLER_FILTER or KHVVIDECFL

    • Data set name: Hyper-V Virtual IDE Controller Win2K12

    Chapter 4. Attributes 25

  • – Table name: KHVVIDECTK– Historical table name: KHV_HYPER_V_VIRTUAL_IDE_CONTROLLER_WIN2K12 or KHVVIDECTK

    • Data set name: Hyper-V Virtual Machine Bus

    – Table name: KHVVMBUS– Historical table name: KHV_HYPER_V_VIRTUAL_MACHINE_BUS or KHVVMBUS

    • Data set name: Hyper-V Virtual Machine Health Summary

    – Table name: KHVVMHESUM– Historical table name: KHV_HYPER_V_VIRTUAL_MACHINE_HEALTH_SUMMARY or KHVVMHESUM

    • Data set name: Hyper-V Virtual Machine Summary

    – Table name: KHVVMSUMMA– Historical table name: KHV_HYPER_V_VIRTUAL_MACHINE_SUMMARY or KHVVMSUMMA

    • Data set name: Hyper-V Virtual Network Adapter

    – Table name: KHVVIRNWAD– Historical table name: KHV_HYPER_V_VIRTUAL_NETWORK_ADAPTER or KHVVIRNWAD

    • Data set name: Hyper-V Virtual Storage Device

    – Table name: KHVVSTORDV– Historical table name: KHV_HYPER_V_VIRTUAL_STORAGE_DEVICE or KHVVSTORDV

    • Data set name: Hyper-V Virtual Switch

    – Table name: KHVVIRSWIT– Historical table name: KHV_HYPER_V_VIRTUAL_SWITCH or KHVVIRSWIT

    • Data set name: Hyper-V Virtual Switch Port

    – Table name: KHVVIRSWPO– Historical table name: KHV_HYPER_V_VIRTUAL_SWITCH_PORT or KHVVIRSWPO

    • Data set name: Hyper-V VM Association with Virtual Network

    – Table name: KHVVMAVCN– Historical table name: KHV_HYPER_V_VM_ASSOCIATION_WITH_VIRTUAL_NETWORK or

    KHVVMAVCN• Data set name: Hyper-V VM IO APIC

    – Table name: KHVVMIOAPI– Historical table name: KHV_HYPER_V_VM_IO_APIC or KHVVMIOAPI

    • Data set name: Hyper-V VM Vid Partition

    – Table name: KHVHYVIDP– Historical table name: KHV_HYPER_V_VM_VID_PARTITION or KHVHYVIDP

    • Data set name: Hypervisor

    – Table name: KHVHYPERVI– Historical table name: KHV_HYPERVISOR or KHVHYPERVI

    • Data set name: Memory

    – Table name: KHVGETMEM0– Historical table name: KHV_MEMORY or KHVGETMEM0

    • Data set name: Memory in Percentage

    – Table name: KHVMEMIPER– Historical table name: KHV_MEMORY_IN_PERCENTAGE or KHVMEMIPER

    26 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • • Data set name: Migration

    – Table name: KHVNVVMIGR– Historical table name: KHV_MIGRATION or KHVNVVMIGR

    • Data set name: Performance Object Status

    – Table name: KHVPOBJST– Historical table name: KHV_PERFORMANCE_OBJECT_STATUS or KHVPOBJST

    • Data set name: Processor

    – Table name: KHVGETPRO0– Historical table name: KHV_PROCESSOR or KHVGETPRO0

    • Data set name: Resource Metering

    – Table name: KHVVMRESME– Historical table name: KHV_RESOURCE_METERING or KHVVMRESME

    • Data set name: Thread Pool Status

    – Table name: KHVTHPLST– Historical table name: KHV_THREAD_POOL_STATUS or KHVTHPLST

    • Data set name: Virtual Machine

    – Table name: KHVGETVIR0– Historical table name: KHV_VIRTUAL_MACHINE or KHVGETVIR0

    • Data set name: Virtual Machine Details

    – Table name: KHVVMOSJOI– Historical table name: KHV_VIRTUAL_MACHINE_DETAILS or KHVVMOSJOI

    • Data set name: Virtual Switch

    – Table name: KHVMSVMVI4– Historical table name: KHV_VIRTUAL_SWITCH or KHVMSVMVI4

    • Data set name: VLAN Endpoint

    – Table name: KHVMSVMVI5– Historical table name: KHV_VLAN_ENDPOINT or KHVMSVMVI5

    • Data set name: VM Mig WO Cluster

    – Table name: KHVVMMIGWC– Historical table name: KHV_VM_MIG_WO_CLUSTER or KHVVMMIGWC

    • Data set name: VM Modification

    – Table name: KHVVMMODF– Historical table name: KHV_VM_MODIFICATION or KHVVMMODF

    • Data set name: VM Operating System

    – Table name: KHVVMOS– Historical table name: KHV_VM_OPERATING_SYSTEM or KHVVMOS

    • Data set name: VM Storage Migration

    – Table name: KHVVMSTMIG– Historical table name: KHV_VM_STORAGE_MIGRATION or KHVVMSTMIG

    Chapter 4. Attributes 27

  • Attribute descriptionsAttributes in each Microsoft Hyper-V Server agent data set collect data that the agent uses for monitoring.

    The descriptions of the data sets contain information such as description, type, and names for eachattribute in the data set. Some attributes are designated as key attributes, which are identifier attributesfor the data set. An attribute in italic indicates that it is available for display in the ApplicationPerformance Dashboard pages.

    Availability data setThe Availability data set contains the availability data for all processes and services that make up thisapplication. This data set is configured for historical collection. Thresholds for this data set are associatedwith the Microsoft Hyper-V Server component. This data set is displayed as KHV AVAILABILITY in thethreshold editor. A data sample is sent to the server every minute and is maintained for 8 days by default.The attributes shown in italic are visible in the UI. All attributes are available for thresholds.

    This data set contains the following attributes:Application Component

    The descriptive name of a part of the application. This attribute is a key attribute. The type is string.

    The following names are defined for this attribute: APPLICATION_COMPONENT or COMPONENT(historical name), Application Component (caption), Application_Component (attribute name), andCOMPONENT (column name).

    NameThe name of the process, service, or functionality test. This name matches the executable name ofthe process, the service short name or the name of the process used to test the application. The typeis string with enumerated values. The following values are defined: N/A (N/A). Any value that does nothave a definition here is displayed in the User Interface.

    The following names are defined for this attribute: NAME (historical name), Name (caption), Name(attribute name), and NAME (column name).

    NodeThe managed system name of the agent. This attribute is a key attribute. The type is string.

    The following names are defined for this attribute: NODE (historical name), Node (caption),ORIGINNODE (attribute name), and ORIGINNODE (column name).

    Percent Processor TimeThe percentage of the elapsed time that this process used the processor to execute instructions. Thetype is integer (32-bit gauge).

    The following names are defined for this attribute: PERCENT_PROCESSOR_TIME or PERCPROC(historical name), Percent Processor Time (caption), Percent_Processor_Time (attribute name), andPERCPROC (column name).

    StatusThe status of the application component.

    • For processes 'UP', 'DOWN', 'WARNING', or 'PROCESS_DATA_NOT_AVAILABLE':'PROCESS_DATA_NOT_AVAILABLE' is displayed for a process when the matching process isrunning but the resource use information cannot be collected for that process.

    • For services 'UP', 'DOWN', or 'UNKNOWN': 'UNKNOWN' is displayed when the service is notinstalled.

    • For functionality tests: 'PASSED' or 'FAILED' is displayed.

    The type is integer with enumerated values. The following values are defined: DOWN (0), UP (1),WARNING (2), UNKNOWN (3), PASSED (4), FAILED (5), PROCESS DATA NOT AVAILABLE (6). Anyvalue that does not have a definition here is displayed in the User Interface.

    28 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • The following names are defined for this attribute: STATUS (historical name), Status (caption), Status(attribute name), and STATUS (column name).

    Thread CountThe number of threads currently allocated by this process. This attribute contains only valid data forprocesses. The type is integer (32-bit gauge).

    The following names are defined for this attribute: THREAD_COUNT or THREADS (historical name),Thread Count (caption), Thread_Count (attribute name), and THREADS (column name).

    TimestampThe local time at the agent when the data was collected. The type is string.

    The following names are defined for this attribute: TIMESTAMP (historical name), Timestamp(caption), Timestamp (attribute name), and TIMESTAMP (column name).

    Working Set SizeThe working set size of the process in MB. This attribute contains only valid data for processes. Thetype is integer (32-bit gauge).

    The following names are defined for this attribute: WORKING_SET_SIZE or WORKSET (historicalname), Working Set Size (caption), Working_Set_Size (attribute name), and WORKSET (column name).

    Command LineThe program name and any arguments specified on the command line when the process was started.For Service or Functionality test, this attribute has the value N/A. The type is string with enumeratedvalues. The following values are defined: N/A (N/A). Any value that does not have a definition here isdisplayed in the User Interface.

    The following names are defined for this attribute: COMMAND_LINE or CMDLINE (historical name),Command Line (caption), Command_Line (attribute name), and CMDLINE (column name).

    Full NameThe full name of the process that includes the path. The type is string with enumerated values. Thefollowing values are defined: N/A (N/A). Any value that does not have a definition here is displayed inthe User Interface.

    The following names are defined for this attribute: FULL_NAME or FULLNAME (historical name), FullName (caption), Full_Name (attribute name), and FULLNAME (column name).

    Functionality Test MessageThe text message that corresponds to the Functionality Test Status. This attribute is only valid forfunctionality tests. The type is string with enumerated values. The following values are defined: N/A(N/A). Any value that does not have a definition here is displayed in the User Interface.

    The following names are defined for this attribute: FUNCTIONALITY_TEST_MESSAGE or FUNCMSG(historical name), Functionality Test Message (caption), Functionality_Test_Message (attribute name),and FUNCMSG (column name).

    Functionality Test StatusThe return code of the functionality test. When the monitored application is running correctly,'SUCCESS' is displayed. 'NOT_RUNNING' is displayed when it is not running correctly. 'N/A' isdisplayed when the row does not represent a functionality test. The type is integer with enumeratedvalues. The following values are defined: SUCCESS (0), N/A (1), GENERAL ERROR (2), WARNING (3),NOT RUNNING (4), DEPENDENT NOT RUNNING (5), ALREADY RUNNING (6), PREREQ NOT RUNNING(7), TIMED OUT (8), DOESNT EXIST (9), UNKNOWN (10), DEPENDENT STILL RUNNING (11),INSUFFICIENT USER AUTHORITY (12). Any value that does not have a definition here is displayed inthe User Interface.

    The following names are defined for this attribute: FUNCTIONALITY_TEST_STATUS or FUNCSTATUS(historical name), Functionality Test Status (caption), Functionality_Test_Status (attribute name), andFUNCSTATUS (column name).

    Chapter 4. Attributes 29

  • Page Faults per SecThe rate of page faults for the process measured in faults per second. This attribute contains onlyvalid data for processes. The type is integer (32-bit gauge).

    The following names are defined for this attribute: PAGE_FAULTS_PER_SEC or PAGEFAULTS(historical name), Page Faults per Sec (caption), Page_Faults_per_Sec (attribute name), andPAGEFAULTS (column name).

    Percent Privileged TimeThe percentage of the available CPU time being used by this process for privileged operation. The typeis integer (32-bit gauge).

    The following names are defined for this attribute: PERCENT_PRIVILEGED_TIME or PERCPRIV(historical name), Percent Privileged Time (caption), Percent_Privileged_Time (attribute name), andPERCPRIV (column name).

    Percent User Mode TimeThe percentage of the available CPU time being used by this process for user mode operation. Thetype is integer (32-bit gauge).

    The following names are defined for this attribute: PERCENT_USER_MODE_TIME or PERCUSER(historical name), Percent User Mode Time (caption), Percent_User_Mode_Time (attribute name), andPERCUSER (column name).

    PIDThe process ID associated with the process. This attribute contains only valid data for processes. Thetype is integer (32-bit gauge).

    The following names are defined for this attribute: PID (historical name), PID (caption), PID (attributename), and PID (column name).

    TypeThe type of the application component. Components are processes, services, or functionality tests.The type is integer with enumerated values. The following values are defined: PROCESS (0), SERVICE(1), FUNCTIONALITY TEST (2). Any value that does not have a definition here is displayed in the UserInterface.

    The following names are defined for this attribute: TYPE (historical name), Type (caption), Type(attribute name), and TYPE (column name).

    Virtual SizeThe virtual size (in MB) of the process. The type is integer (32-bit gauge).

    The following names are defined for this attribute: VIRTUAL_SIZE or VIRTSIZE (historical name),Virtual Size (caption), Virtual_Size (attribute name), and VIRTSIZE (column name).

    Director data setThe Director data set provides information about the configuration settings of the IBM Systems Director.

    This data set contains the following attributes:Director Port

    The port number of the Director Server. The type is string.

    The following names are defined for this attribute: DIRECTORPORT or DPORT (historical name),Director Port (caption), DirectorPort (attribute name), and DPORT (column name).

    Director ServerThe name of the Director Server. The type is string.

    The following names are defined for this attribute: DIRECTORSERVER or DSERVER (historical name),Director Server (caption), DirectorServer (attribute name), and DSERVER (column name).

    30 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent:Microsoft Hyper-V Server agent Reference

  • NodeThe managed system name of the agent. This attribute is a key attribute. The type is string.

    The following names are defined for this attribute: NODE (historical name), Node (caption),ORIGINNODE (attribute name), and ORIGINNODE (column name).

    TimestampThe local time at the agent when the data was collected. The type is string.

    The following names are defined for this attribute: TIMESTAMP (historical name), Timestamp(caption), Timestamp (attribute name), and TIMESTAMP (column name).

    Use TEP CredentialThe TEP credentials details that are used for accessing authentication to the IBM Systems Director.The type is string.

    The following names are defined for this attribute: USETEPCREDENTIAL or TEPUSER (