Discovery with the agent
Collector Type: Agent
Category: Application Monitors
Application Name: HyperV-Memory
Global Template Name : Microsoft Hyper-V Memory Performance Counters DotNet v4
Collected Metrics
| Metric Name | Display Name | Description |
|---|---|---|
| Memory_averagepressure | Memory_averagepressure | The average pressure on the balancer node. This privides a view of the overall memory allocation of your system. A virtual machine with a pressure of 100 has exactly the amount of memory that it needs (this is equivalent to a memory availability of 0%). If the virtual machine pressure goes over 100,it now has less memory than it needs (equivalent to a negative memory availability) and if the virtual machine pressure is under 100 then the virtual machine has more memory than it needs. Ideally this value should be at 80 or lower. The closer this gets to 100, the closer you are to running out of memory. Once this number goes over 100 it indicates that there are virtual machines that are paging in the guest operating system. |
| Memory_availablebytes | Memory_availablebytes | The current amount of memory (in MB) that is available on the balancer node. |
| Memory_PagesPerSecond | Memory_PagesPerSecond | This performance monitor counter measures the rate at which pages are read from or written to disk to resolve hard page faults. To resolve hard page faults, the operating system must swap the contents of memory to disk, which negatively impacts performance. A high number of pages per second in correlation with low available physical memory may indicate a lack of physical memory. A value lesser than 500 is considered healthy. |
| Memory_HypervisorRootPartitionValue2MGPApages | Memory_HypervisorRootPartitionValue2MGPApages | This monitor returns the number of 2M pages present in the Guest physical addresse GPA space of the partition. This counter indicates whether or not a VM is using large memory pages which improves overall VM performance. |
| Memory_HypervisorRootPartitionDepositedPages | Memory_HypervisorRootPartitionDepositedPages | TThis monitor returns the number of pages deposited into the partition. It shows how much memory the hypervisor is using for managing the system. |
| Memory_HypervisorRootPartitionVirtualProcessors | Memory_HypervisorRootPartitionVirtualProcessors | The number of virtual processors that exist in the partition. |
| Memory_HypervisorPartitionValue2MGPApages | Memory_HypervisorPartitionValue2MGPApages | This monitor returns the number of 2M pages present in the Guest physical addresse GPA space of the partition. This counter indicates whether or not a VM is using large memory pages which improves overall VM performance. |
| Memory_HypervisorPartitionDepositedPages | Memory_HypervisorPartitionDepositedPages | For each partition, the hypervisor maintains a memory pool of RAM System physical address (SPA) pages. Pages can be deposited into or withdrawn from the pool. This monitor returns the number of pages deposited into the partition. It shows how much memory the hypervisor is using for managing the VM. |
| Memory_HypervisorPartitionVirtualProcessors | Memory_HypervisorPartitionVirtualProcessors | This monitor returns the number of virtual processors presented in the partition and configured to use by the VM. |
| Memory_PhysicalPagesAllocated | Memory_PhysicalPagesAllocated | The Virtual Interface Driver (VID) counters account for the guest address space and any additional memory the VID needs to manage the virtual machine. This counter is the total number of guest pages and VID pages needed to manage the VM. |
| Memory_RemotePhysicalPages | Memory_RemotePhysicalPages | The Virtual Interface Driver (VID) counters account for the guest address space and any additional memory the VID needs to manage the virtual machine. The number of physical pages that are not allocated from the preferred Non-Uniform Memory Access (NUMA) node. This counter lets you know on NUMA based systems if a VM is spanning multiple nodes. |