Microsoft Hyper-V InfrastructureMicrosoft Hyper-V Infrastructure
Monitor health and performance of the Hyper-V clusters, hosts and VMs.
Extension
- Product information
- Release notes
Overview
This extension monitors performance of the Hyper-V fabric, tracking health, performance and resource utilization of the Hyper-V VMs, together with the context of their host and cluster resources. Hyper-V extension leverages PowerShell cmdlets and WMI to collect data from the Windows hypervisor, following best practices employed by Microsoft, as well as Dynatrace customers who contributed to validation of this extension in real-life situations.
This is intended for users, who:
Want to get full monitoring for their Hyper-V clusters, detect problems ahead of serious impact, and pinpoint the root cause in their virtualization and application layer, including:
- Processor bottlenecks
- Memory bottlenecks
- Network bottlenecks
- Storage bottlenecks
- Dependent applications hosted on the Hyper-V cluster
Use cases
This extension enables you to:
- Monitor health and performance of your Hyper-V cluster, using built-in analysis screens and easy-to-navigate dashboards
- Make sure resources are split optimally between the virtual machines
- Relate performance of the applications and VMs monitored with OneAgent to the underlying Hyper-V resources allotted to the VMs
Get started
This extension is executed by the OneAgent (local monitoring). To start, simply activate the extension in your environment using the in-product Hub, and provide a Windows user account with at least the following permissions:
- Hyper-V Administrators group
- Read access to the cluster, check with Get-ClusterAccess
- Read and Write access to the Windows TEMP directory
Details
Metrics collected:
- VMs’ health
- Memory usage
- CPU utilization
- Storage operations
- Network traffic
This extension is built on top of the Extension Framework 2.0 and delivers:
- Configuration required to drive the Hyper-V PowerShell cmdlets execution and scrape metrics from them
- A Dashboard
- Topology definitions
- Unified Analysis screens
Compatibility information
This extension requires:
- x64 OS with BIOS-activated virtualization:
- Windows 10 Enterprise/Pro/Education
- Windows Server 2016 or newer
Note on topological relationships between discovered Hyper-V VMs and OneAgent-monitored VM instances:
- Starting with release 2.0.13, this extension maintains SAME_AS relationship between discovered VMs and OneAgent-monitored instances of the guest OS, using IP address as the join property.
- This relationship enables:
- Davis AI analytics to look together at metrics obtained by this extension and from OneAgent, to completely characterize monitored guest OS instances performance
- Discovery and Coverage app to suggest which discovered VMs should be instrumented with OneAgent for full visibility into performance
- This relationship works for known Windows guest OSes, but has limitations when guest OS is Linux. This limitation stems from the fact that on Hyper-V, Linux guest OS should be instrumented with the Microsoft's Linux Integration Service, while this service supports limited spectrum of the Linux distributions. See the link for details.
Q&A
Q: What is the DDU Consumption of this extension?
A: The formula for DDU consumption of the extension is:
( ( 3 * number of Clusters)
+ ( ( 9 * number of Hosts)
+ ( ( 6 * number of VMs)
+ ( ( 4 * number of Storage Devices)
+ ( ( 4 * number of Virtual Storage Devices)
+ ( ( 6 * number of NICs)
+ ( ( 6 * number of vNICs) ) * 525.6 DDUs/year
DDU cost above does not include any possible Log events or Custom events triggered by the extension. For more information on this, please visit the DDU log event cost and DDU custom event cost pages.
Extension content
Content typeNumber of items included
screen layout
7
list screen layout
7
screen injections
1
screen properties
2
screen entities lists
11
generic type
7
screen chart groups
16
alerts
10
metric query
9
dashboards
1
generic relationship
8
metric metadata
50
Feature sets
Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.
Feature setsNumber of metrics included
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Network Packets Sent | hyperv.virtual_machine.network_interface_card.packets_sent | - | PerSecond |
| Network Packets Received | hyperv.virtual_machine.network_interface_card.packets_received | - | PerSecond |
| Network Packets Transferred | hyperv.virtual_machine.network_interface_card.packets_transferred | - | PerSecond |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| CPU Utilization | hyperv.host.cpu_utilization | - | Percent |
| Logical CPU Count | hyperv.host.logical_cpu_count.gauge | - | Cores |
| Physical CPU Count | hyperv.host.physical_cpu_count.gauge | - | Cores |
| CPU Reserve | hyperv.host.cpu_reserve | - | Percent |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Network Packets Sent | hyperv.host.network_interface_card.packets_sent | - | BytePerSecond |
| Network Packets Received | hyperv.host.network_interface_card.packets_received | - | BytePerSecond |
| Network Packets Transferred | hyperv.host.network_interface_card.packets_transferred | - | BytePerSecond |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Disk Read Rate | hyperv.virtual_machine.storage_device.read_rate | - | PerSecond |
| Disk Write Rate | hyperv.virtual_machine.storage_device.write_rate | - | PerSecond |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Disk Read Rate | hyperv.host.disk.read_rate | - | PerSecond |
| Disk Write Rate | hyperv.host.disk.write_rate | - | PerSecond |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Network Bytes Sent | hyperv.host.network_interface_card.bytes_sent | - | BytePerSecond |
| Network Bytes Received | hyperv.host.network_interface_card.bytes_received | - | BytePerSecond |
| Network Bytes Transferred | hyperv.host.network_interface_card.bytes_transferred | - | BytePerSecond |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Total Disk Size | hyperv.host.disk.total_size | - | Bytes |
| Available Disk Space | hyperv.host.disk.space_free | - | Bytes |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| CPU Count | hyperv.virtual_machine.cpu_count.gauge | - | Cores |
| CPU Reserve | hyperv.virtual_machine.cpu_reserve | - | Percent |
| CPU Utilization | hyperv.virtual_machine.cpu_utilization | - | Percent |
| Total Memory | hyperv.virtual_machine.total_memory | - | Bytes |
| Used Memory | hyperv.virtual_machine.used_memory | - | Bytes |
| Memory Pressure | hyperv.virtual_machine.memory_pressure | - | Percent |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Virtual Machine Count | hyperv.host.virtual_machine_count.gauge | - | Count |
| Running Virtual Machine Count | hyperv.host.running_virtual_machine_count.gauge | - | Count |
| Uptime | hyperv.host.uptime | - | Seconds |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Network Bytes Sent | hyperv.virtual_machine.network_interface_card.bytes_sent | - | BytePerSecond |
| Network Bytes Received | hyperv.virtual_machine.network_interface_card.bytes_received | - | BytePerSecond |
| Network Bytes Transferred | hyperv.virtual_machine.network_interface_card.bytes_transferred | - | BytePerSecond |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Total Memory | hyperv.host.total_memory | - | KiloByte |
| Available Memory | hyperv.host.available_memory | - | KiloByte |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Total Disk Space | hyperv.virtual_machine.storage_device.total_disk_space | - | Byte |
| Used Disk Space | hyperv.virtual_machine.storage_device.used_disk_space | - | Byte |
Related to Microsoft Hyper-V Infrastructure
Full version history
To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate
Full version history
Patch level changes:
- Changed way of reading the cluster name to PowerShell instead of WMI - to address an issue with access permissions
Full version history
New features
- Generate a log event when a VM is moved between hosts
Patch level changes
- Fixed issue with multiple threads modifying the same list of VMs
- Improve error handling for WMI queries
Full version history
Patch level changes:
- Added ability to set a debug log level and the collection frequency
- A fix for an incorrect count of VMs on one of the UA screens
Full version history
Patch level changes:
- Fix locks that hindered performance and clean up the VM stats
Full version history
Enhancements:
- Added option to use the credential vault to manage user credentials required by the extension
Patch level changes:
- Split VM collection into 3 separate "query" methods to improve execution time
- Added sourceEntityType for all metrics
Full version history
Fixed alert json for func: metrics since they were using metricId instead of metricSelector.
Full version history
Added SAME_AS relationship between discovered VMs and OneAgent-monitored instances of the guest OS, using IP address as the join property. This relationship enables:
- Davis AI analytics to look together at metrics obtained by this extension and from OneAgent, to completely characterize monitored guest OS instances performance
- Discovery and Coverage app to suggest which discovered VMs should be instrumented with OneAgent for full visibility into performance
Stated the requirement that Windows user account who runs the extension requires Read and Write access to the Windows TEMP directory.
Full version history
This release introduces an important change: Hyper-V extension requires local activation now (i..e. activation on an OneAgent-instrumented host).
Previous releases allowed remote installation (i.e. activation on an ActiveGate), but because of Hyper-V specifics, this very often caused permission issues that severely limited extension functionality and weren't solvable. So anyway - we have been advising you to move to local activation. Now it's the only way to activate this extension.
Additionally, this release fixes some issues with filtering monitored entities.
Full version history
Fixed reporting of the rate metrics and occasional issues with metric extraction from nested environments.
Full version history
Fixed a bug affecting extension activation under certain conditions. Extension logs on affected systems reported "AttributeError: 'dict' object has no attribute 'feature_sets' "
Full version history
Release notes
Release 2.0.0
- Extension has been re-written to leverage PowerShell cmdlets instead of WMI metric retrieval
- PowerShell cmdlets enable the extension to retrieve focused metrics that are essential to Hyper-V performance monitoring
- PowerShell cmdlets are instantiated using Python runtime, to control execution and assure required permissions to access specifc metric counters
