f Microsoft Hyper-V Monitoring | Complete VM Visibility

You are here

Microsoft Hyper-V Agentless Monitoring

Requires Opsview Cloud or Opsview Monitor 6.6
check_circle
Opsview Supported

Microsoft Hyper-V Server Agentless Monitoring

Formerly known as Windows Server Virtualization, Hyper-V is Microsoft’s popular virtualization system for Windows Servers. It provides virtualization software for operating systems as well as hardware components such as, hard drives and network switches. Virtualization and Hyper-V offer numerous benefits, such as; hardware resources savings, space savings and reductions in energy costs, amongst many others. As a result it has become an incredibly popular hypervisor across the globe.

What You Can Monitor

This opspack allows you to monitor your host and guest systems, ensuring they are performant on all of your Windows Servers, providing service checks for CPU, Memory, Storage and Uptime, as well as important information on health statuses.

Service Checks

Service Check Description
CPU Hyper-V guest CPU load percentage
GuestStatus Hyper-V Guest Status
Health Hyper-V guest health status
Memory Hyper-V guest memory available
StorageErrors Hyper-V guest storage errors
StorageRead Hyper-V guest storage read rate
StorageWrite Hyper-V guest storage write rate
Uptime Days Virtual Machine Uptime in Days
Uptime Seconds Virtual Machine Uptime in Seconds
Virtual Machines List all Virtual Machines

Prerequisites

Ensure your Opsview Monitor version is at least 6.6.7. Check Opsview Release Notes for the latest version of Opsview Monitor.

Setup Windows Host for Monitoring

To use Windows WMI Agentless Opspacks, the remote windows host must first be configured to allow WMI queries to be run. See: Monitoring Services with WMI.

Setup and Configuration

To configure and utilise this Opspack, you need to add the 'Application - Microsoft - Hyper-V Agentless' Opspack to your Opsview Monitor system.

Step 1: Add the host template

Add the Application - Microsoft Hyper-V Agentless Host Template to your Opsview Monitor host.

For more information, refer to Opsview Knowledge Center - Adding Host Templates to Hosts.

Step 2: Add and configure variables required for this host

Variable Description
WINRM_TRANSPORT Used for authenticating with the remote host. The Value is the Authentication Transport Type - must be one of: Basic, Certificate, Kerberos or NTLM. NOTE: CredSSP is not supported. Override the Username and Password with the credentials to be used for authentication with the remote host. Scheme can be overridden to make the check use HTTP (defaults to https). Extra arguments can be used to pass extra arguments to check_by_winrm.py
KERBEROS_REALM Only required if authenticating using Kerberos. The Value is the Kerberos realm.

Step 3: Apply changes and the system will now be monitored

Microsoft Hyper-V Agentless Service Checks