How to monitor VMWare using Kaseya Network Monitor 4.1

With the release of Kaseya Network Monitor version 4.1, we now have two built-in ways of monitoring your VMware infrastructure. We support versions 4.1 and 5.0 of ESX/ESXi from build 7345.

With the Lua script that comes with the install package, you can easily setup monitoring of the most common health counters’ operational status. The counters that are checked are the following:

  • CPU
  • Storage volumes
  • Storage Extent
  • Controller
  • SATA ports
  • Memory
  • Power supply
  • Fan

The script checks for any abnormalities in the operational status for each counter and will set an alarm if the status is not in an OK state.

To start monitoring, first you need to create an object choosing VMware as the operating system and then choose version (ESX 4.1, ESXi 4.1 or ESXi 5.0).

How to monitor VMWare with KNM 1

When you choose Vmware as the template, you will see the following options for choosing monitors. The new options for version 4.1 is the built-in Lua script for health and the VMware performance monitor.

How to Monitor VMWare using KNM 4.1 2

VMware Health Check

For the health check Lua script, choose “WBEM_ESXi_Health_.lua” script. In most cases, you can leave “Secure” and “Ignore not found” as True, which is their default values. Also make sure you select a logon account (Use object default account is default) and check “No account logon.”

How to monitor VMWare with KNM 4.1 3

For the display results of this monitor, you will just see “Test OK” in the status windows as long as the operational status for the tested hardware is OK.

How to monitor VMWare using KNM 4.1 4

If any of the performed tests would fail, the details of what part that failed will be shown in the status field and will be included in the alarm event.

VMware Performance Monitor

When setting up this montor, it will automatically check what performance counters that are available for your version of ESX/ESXi. For detailed information about the counters, refer to your VMware version’s documentation.

How to monitor VMWare using KNM 4.1 5

In this example, the counter ”rescpu.active5.latest” was chosen. This counter will show the CPU’s last 5 minute’s average activity in percent from VMware.

The “Data Type” in this case should be chosen as “CPU Utilization.” Please refer to the KNM Documentation for creating your own data types.

In the “Comparison Options”, you could for example set that this monitor should pass if the current average CPU load during 5 minutes is less than 50% or trigger an alarm if over 50%.

Click on ”Save” and this is how the monitor will look like in KNM.

How to Monitor VMWare using KNM 4.1 6

If we then create a report from the collected data, in this case on a ESXi 4.1 system with some more load, it could look something like this.

How to monitor VMWare using KNM 4.1 7

Below is how the monitoring could be configured for an ESXi 5.0 system. We have CPU load during the last 5 minutes, memory average usage, network average usage plus the health check Lua script configured for this object.

How to monitor VMWare using KNM 4.1 8

Click here to learn more about Kaseya Network Monitor.

7 Responses to “How to monitor VMWare using Kaseya Network Monitor 4.1”

  1. Kerry March 23, 2012 at 4:30 pm #

    Interesting… in the KNM webinar the other day, it was pretty clearly stated that there was no current support for ESXi 4.1. I can’t imagine this changed in the last couple days – maybe a correction to the article is needed? Or am I crazy?

    • Tomas Andersson March 24, 2012 at 12:35 am #

      Hi Kerry,

      The initial release of 4.1 did not support ESXi 4.1, you are absolutely right about that. The webinar was based on the initial release and since then, we have found a bug that limited us to not being able to monitor ESXi 4.1. In the beginning of this article, we also put build 7345 as a requirement. That is the most current release that is available on our download site.

      We are sorry for any confusion on the matter but the limitation was only recently removed so we changed the blog post in the last minute before publishing it.

      Best regards,

      Tomas Andersson
      Quality Assurance Engineer
      Kaseya

      • Kerry March 24, 2012 at 6:37 pm #

        Wow… that’s a big deal for our implementation. Great news on the bug fix – thanks for the tip!

      • Dias April 9, 2012 at 3:15 pm #

        Hi Tomas,

        I just wanted to know if I can monitor Datastores as well just incase it runs out of space.

        • Tomas Andersson October 7, 2013 at 5:27 am #

          A very long time after your question, but I was browsing through the blog post just now and thought I’d reply. Since a few months ago, we do have a datastore utilization monitor built in. It will be automatically added during Discovery, or if you click on “Inspect now” in KNM v5. It can also be added manually.

  2. Richard Lemon December 13, 2012 at 3:57 pm #

    Will KNM 4.1 monitor ESXi 5.1 systems in the near future? Will it have support for IE10 on Windows 8 soon?

    Thanks

    • Tomas Andersson October 7, 2013 at 5:29 am #

      KNM v5 supports all current versions of VMware. I am not aware of any limitations when using IE10 or Windows 8 as the client platform.

Leave a Reply:

Gravatar Image

-->