How To Monitor Hyper-V and ESX servers

Monitoring Hyper-V servers with the Atera agent

The Agent should be installed both on the Hyper-V server and on the individual VMs running on it. This will provide both Hyper-V specific data and alerts as well as specific VM data.

The agent should be installed on the Main Hyper-V Server using the Atera installation tool.

Examples for monitored data/information:

• Hyper-V-Config
• Hyper-V-High-Availability
• Hyper-V-Hypervisor
• Hyper-V-Image-Management-Service
• Hyper-V-Integration
• Hyper-V-Network

Click here for a detailed external article on the Hyper-V event log.

In addition, an Agent should be installed on each individual Virtual Machine to monitor its performance. Click here for detailed instructions on installing the Atera Agent on Windows machines.

Monitoring an ESX server with SNMP

Simply add specific OIDs that are related to the server performance when creating an SNMP device + (Upper Menu) -> Create New Device -> SNMP Device.

For details on creating an SNMP devices and adding OIDs click here

Note: We have collected useful examples for monitoring ESXi, Disk Failures, Memory and CPU

You can find more OIDs in the following links:

http://www.oidview.com/mibs/80/NETSERVER-MIB.html

https://pastebin.com/ngmxqgJb

Examples:

• Disk Failures – Disk failure is represented by object namehrStorageAllocationFailures, where the OID is.1.3.6.1.2.1.25.2.3.1.7.1. The value you should receive will be either 0 or other number representing the number of errors that occurred. In order to receive a Critical Alert in your Atera dashboard, you should add.1.3.6.1.2.1.25.2.3.1.7.1 to the monitored OID; then set a condition of greater than 0; and of course Alert Severity should be set to Critical.
• Memory (Used)– The server’s used memory is represented by object namehrStorageUsed, where the OID is.1.3.6.1.2.1.25.2.3.1.6.11. To get an alert on your Atera dashboard, add .1.3.6.1.2.1.25.2.3.1.6.11 to the monitored OID with the condition of greater than 4441124, and Alert Severity as Warning.
• CPU - The CPU entry is represented by object namehrProcessorLoad. Add the following pattern to the 'Discover' window: .1.3.6.1.2.1.25.3.3.1.2; you should receive a list of Cores. In order to monitor Core #8 use.1.3.6.1.2.1.25.3.3.1.2.8 to the monitored OID, with condition Greater than 60, and Alert Severity set to Critical

In addition, install an agent on each individual machine to monitor its specific, individual performance.