{"id":31514,"date":"2022-04-14T15:00:32","date_gmt":"2022-04-14T14:00:32","guid":{"rendered":"https:\/\/www.n-able.com\/?p=31514"},"modified":"2022-04-14T11:52:11","modified_gmt":"2022-04-14T10:52:11","slug":"monitoring-hyper-v-and-esxi-what-should-you-do","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/es\/blog\/monitoring-hyper-v-and-esxi-what-should-you-do","title":{"rendered":"Monitoring Hyper-V and ESXi\u2014what should you do?"},"content":{"rendered":"

Over the years, I found that building out monitoring scripts and using them properly has proven to be a challenge. When I look back at my internal IT days using platforms like Whatsupgold, PRTG, or N‑central, the question always remained the same: how can I monitor efficiently and get alerts that matter?<\/p>\n

In this blog post, I thought I\u2019d tackle something that is a challenge for a lot of people: monitoring Hypervisors. For the purposes of this piece, I\u2019m going to focus on the two main ones: Hyper-V and ESXi.<\/p>\n

I will look at this from the point of view of fairly general concepts, so no matter what tool you use, you should see if what I\u2019m suggesting fits your needs and apply what is appropriate to you and your environment.<\/p>\n

Monitoring Hyper-V<\/h2>\n

Let\u2019s start with Hyper-V, as this is likely the simplest one. Most people I talk to that monitor Hyper-V usually focus on two areas:<\/p>\n

    \n
  1. Physical health<\/li>\n
  2. OS\/Hypervisor health<\/li>\n<\/ol>\n

    On the physical health side, this is usually done by working with the host\u2019s management layer. For example, Dell and HP servers have software that is installed in Windows that allows you to get health data through API\/SNMP. This will give you the health of the power supplies, various modules (RAM, CPU, etc.), as well as Raid cards, drive health, etc. Personally, I try to focus on the obvious things that usually cause major issues. These tend to be, in no particular order:<\/p>\n